Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Think of moving the whole deployment to docker #22

Open
charliwest opened this issue Oct 18, 2018 · 3 comments
Open

Think of moving the whole deployment to docker #22

charliwest opened this issue Oct 18, 2018 · 3 comments

Comments

@charliwest
Copy link
Contributor

Hello,

Had some free time and was setting up 2 ispindels and wanted to test them with the csv method before moving onto anything more complex.

Anyway, long story short, I docker-ised the set up (currently for csv only) over at https://github.com/charliwest/iSpindel-Service-docker.

Still some work to do to make it fuller, but the basics work already.

@DottoreTozzi
Copy link
Owner

Nice. Keep us updated!

@avollkopf
Copy link
Contributor

What sort of docker are you using? Mine is running on a qnap in a container. Configuration depends on what database you are using. I did not want to use a separate database and access the main DB of the qnap system. This allows me to access and display that data e.g. in WordPress under my regular Apache on the qnap.

@charliwest
Copy link
Contributor Author

charliwest commented Nov 7, 2018

What sort of docker are you using?

At this moment I am using it on a PI, I am looking into how to cross build it for multi platform (using this as a learning experience for me to use docker)

Configuration depends on what database you are using.

Yes, at the moment this is JUST the python process, I had it writing to a csv, I have also spun up a mariadb container and had it write to the db there. I want to try and keep these things separate, as that is the point of docker. You can of course use the iSpindel-service-docker to write to multiple locations.
By the sound of it you can just change the location the python writes to as normal and just point it to the db you want it to write to, as mentioned I have tested the db part and it seems to work just fine.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants