Inventory management system
Go to file
palid 9983511136
fix: ignore new devcontainer files
2024-02-04 16:13:34 +01:00
.devcontainer fix: ignore new devcontainer files 2024-02-04 16:13:34 +01:00
.vscode dx: Un-ignore .vscode 2024-02-01 12:49:36 +01:00
auth Revert "auth: do not automatically staff new members" 2023-08-25 21:51:09 +02:00
readme feat: Add awesome devcontainer intro and better readme 2024-02-01 12:49:36 +01:00
spejstore fix: server static on s3 correctly 2024-01-19 22:31:39 +01:00
static errors: add cute error pages 2023-08-25 21:04:43 +02:00
storage fix printing 2024-01-31 09:25:15 +01:00
templates fix: properly create svgs static paths 2024-01-31 14:22:17 +01:00
.dockerignore feat: Add awesome devcontainer intro and better readme 2024-02-01 12:49:36 +01:00
.env.example cleanup: docker-compose and .env.example 2024-01-19 19:22:36 +01:00
.gitignore fix: ignore new devcontainer files 2024-02-04 16:13:34 +01:00
Dockerfile fix: run app as spejstore user, not root 2024-02-01 12:49:36 +01:00 fix: readme typo 2024-02-04 16:00:22 +01:00
docker-compose.yml feat: Add awesome devcontainer intro and better readme 2024-02-01 12:49:36 +01:00 Initial commit 2016-09-30 00:04:43 +02:00
requirements.txt fix: correctly lock all dependencies 2024-02-01 12:49:37 +01:00
spejstore-dev.env fix: weird docker compose hacks 2024-01-13 23:30:50 +01:00

spejstore (AKA inventory)

The general HSWAW (and other polish hackerspaces) inventory system.

Because there is not enough general inventory software invented here yet.


Quick start (VSCode)

  1. Copy .env.example as .env
  2. Have docker compose 2.0. You can identify it by having docker compose command instead of docker-compose.
  3. Customize your .env for your specific usecase.


  1. Setup environment variables
  2. Get VSCode from here, CAN NOT be VSCodium, as the extension is a microsoft binary which does not work with VSCodium.
  3. Install Dev Containers extension
  4. Clone the repository and open it with VSCode.
  5. You should get a toast like this when re-opening directory with the cloned repository. Toast example
    1. If you don't get a toast, then use (CMD|Ctrl)+Shift+P to open actions menu and choose option Rebuild Without Cache and Reopen in Container. Command example
  6. Reopen the directory in container either via command or popup button.
  7. Wait for the application and container to properly build.
    1. Devcontainer's VSCode instance will be automatically configured with extensions to help your development process.
    2. You might get a Toast telling you to re-open the directory due to Black not working properly. Do so for proper autoformatting support.
    3. Make sure that extensions were installed in your vscode devcontainer. It might take a couple of minutes.
  8. migrate will be run automatically after container creation, to make sure you have the latest migrations done on the development database without any need for interaction.
  9. Run debug session with either command of "Start Debugging" (default hotkey F5), or with the Debug sidebar. Debug sidebar instructions
  10. You should have automatically forwarded ports, so the only thing remaining is opening browser window with the url provided in terminal.

Everything else (docker)

  1. Run docker compose up. This will create a production-ready setup with gunicorn. out of the box.

Everything else (python)

  1. Get python3
  2. pip install -r requirements.txt
  3. python3 migrate
  4. python3 collectstatic
  5. python3 runserver

New docs (WIP)

Spejstore is a simple inventory system made for Warsaw Hackerspace purposes. Includes some features very specific to hswaw requirements, which are:

  • Label printing and label-system support (via django-rest-api api views and SPEJSTORE_LABEL_API env variable), using the spejstore-labelmaker software
  • Publically viewing all items and requiring users to sign in view oauth to manage inventory via django-admin
  • Authorizing label printing via local network only, see SPEJSTORE_LAN_ALLOWED_ADDRESS_SPACE env variable

Currently inventory is deployed under, with a Beyondspace NGINX configuration, which allows the inventory to be accessible from outside of the Warsaw Hackerspace network with a necessary oauth authorization, but does not allow printing of labels without physically being in the local network of HSWAW.