This application generates STL or STEP files of configurable Gridfinity compatible components. For example, for the standard divider bin you can specify width, length, height, number of compartments (in both directions) and whether or not you want a stacking lip, magnet holes, screw holes, curved scoop surface and/or one or more label tabs. Here are some of the possible bins you can create in this way: The total number of possible combinations with those options is beyond one million, which is why the 3D models are dynamically created and not pre-calculated.
There are currently a few components available, listed below. Other components are in the works.
- Baseplate: Basic baseplate without screws, magnets or weighting.
- Divider bin: Standard divider bin very similar to Zack's original design.
- Light bin: A light version of the normal Gridfinity bin that saves plastic and offers more room. This means there is no room for magnets and/or screws
- Solid bin: A completely filled solid Gridfinity bin which can be used as a starting point for custom bins
- Holey bin: A solid bin with a grid of holes of user-defined shape, size and depth. Includes option for a keepout-area around each hole
If you don't know how to run your own server (or simply don't want to), there should be an instance of the generator running at https://gridfinity.bouwens.co. No uptime guarantees, but it has been running since early 2023 and seems stable enough, even with the occasional spike in load.
The generator runs as a web-application in a docker container. To run your own instance, perform the following steps from the command line:
- Download and unzip the code or clone the repository:
git clone https://github.com/jeroen94704/gridfinitycreator
- cd into the source directory
- Build the Docker Image:
./build.sh
(may need to prefix this with 'sudo') - Start the server:
./deploy.sh
(may need to prefix this with 'sudo')
Now you can access the application by opening a browser and navigating to :5000, e.g.
http://192.168.1.100:5000/
The deploy script results in the server running in production mode using the Waitress WSGI server. This is good for performance, but if you want to debug the code, start the server using the "./debug.sh" script instead of "./deploy.sh". This will make the server start itself using the built-in Flask server, which has convenient debugging features.
Because I use Traefik myself I included the Traefik labels I use in the docker-compose file. If you want to use Traefik, uncomment them and comment out the "ports" section. You will also need to fill in your domain in the .env.container file.
I have no experience with other reverse proxy methods (Apache, nginx, Helm, etc), so if anyone creates instructions for setting up GridfinityCreator with any of those I'd happily accept the pull-request.
Kirk Kirkconnell 🤔 |
wug-ge 🐛 |
Chase Bolt 🐛 |
If you find this project useful a small donation is much appreciated (but by no means required or expected): https://ko-fi.com/jeroen94704
GridfinityCreator © 2023 by Jeroen Bouwens is licensed under CC BY-NC-SA 4.0. To view a copy of this license, visit http://creativecommons.org/licenses/by-nc-sa/4.0/