snypy / snypy-docker

Docker setup for running SnyPy
MIT License
33 stars 3 forks source link

Deployment issue #21

Open Monkey999Human opened 1 year ago

Monkey999Human commented 1 year ago

I am writing to inform you about an issue I am facing with setting up the snypy-docker instance of your program. I have been attempting to get it up and running for the past hour, but unfortunately, I have been unsuccessful so far. I am really excited to use your program and would greatly appreciate your assistance in resolving this problem.

I have attempted two different methods to deploy the program: using manual commands with Docker Compose and trying it through Portainer. Regrettably, neither approach has yielded the desired results. The program is still not functioning correctly, and I am unsure what steps to take next.

In light of this, I wanted to inquire if it would be possible for you to provide a file that I can include in a stack deployment for Portainer. Having a preconfigured file would simplify the deployment process and ensure the correct setup for your program. It would be particularly helpful if you could incorporate variables that can be easily filled in, allowing for easier customization and configuration during the deployment process.

Additionally, I would like to know if there is a way to view the open ports in Portainer once the program is deployed. Having this information would be immensely helpful for troubleshooting and for visual comfort.

I apologize for any inconvenience caused by this support ticket, and I appreciate your prompt attention to this matter. Thank you in advance for your assistance. Please let me know if there are any further details or logs that I can provide to help diagnose the issue.

Looking forward to your response.

juanyunis commented 12 months ago

If you still have problems trying to make it work, I was successfully able to run it. I did have to create a better docker-compose.yml that is 100% compatible with Portainer. Please see attached YAML file for portainer and also .env file that you can load with portainer. You have to modify the env vars with your desired values.

  1. Portainer docker-compose.yml
  2. Portainer .env file that you can load/import while creating the stack

Once you are successfully able to create the stack/containers, please login into the api console (using portainer or docker) and create a file in fixtures folder named setup.json and copy the contents from this url setup.json fixture and then run: python manage.py loaddata fixtures/setup.json

After doing this you should be able to login into the admin panel with: username: admin password: 12345678!

pommetjehorlepiep commented 8 months ago

If you still have problems trying to make it work, I was successfully able to run it. I did have to create a better docker-compose.yml that is 100% compatible with Portainer. Please see attached YAML file for portainer and also .env file that you can load with portainer. You have to modify the env vars with your desired values.

  1. Portainer docker-compose.yml
  2. Portainer .env file that you can load/import while creating the stack

Once you are successfully able to create the stack/containers, please login into the api console (using portainer or docker) and create a file in fixtures folder named setup.json and copy the contents from this url setup.json fixture and then run: python manage.py loaddata fixtures/setup.json

After doing this you should be able to login into the admin panel with: username: admin password: 12345678!

@juanyunis the FRONTEND_URL & BACKEND_URL in the .env file are swapped around I think...

Correct values should be:

BACKEND_URL=https://api-my-domain.com FRONTEND_URL=https://my-domain.com

nezhar commented 1 month ago

I would really appreaciate if you can directly do a pull request in future. I may consider adding the migrations on startup, maybe with a custom entrypoint script.