Add docker-compose for development containers#148
Add docker-compose for development containers#148ArtOfCode- merged 4 commits intocodidact:developfrom
Conversation
Signed-off-by: vsoch <[email protected]>
Signed-off-by: vsoch <[email protected]>
Signed-off-by: vsoch <[email protected]>
vsoch
force-pushed
the
add/docker-compose
branch
from
419dd85 to
9f4e7d2
Compare
|
I added an environment variable to check if the PR is a fork, because it will fail in that case (and I don't think you'd want to try doing some kind of deploying from some rando person submitting a PR?) |
| password = ENV['COMMUNITY_ADMIN_PASSWORD'] || 'password' | ||
| email = ENV['COMMUNITY_ADMIN_EMAIL'] || '[email protected]' | ||
|
|
||
| User.create(username: username, password: password, email: email, is_global_admin: true, is_global_moderator: true, staff: true) |
There was a problem hiding this comment.
Is there a reason that we can't just set confirmed_at here too?
There was a problem hiding this comment.
I tried this approach - it didn't work. I'm not sure why, to be honest. But re-thinking it, in the same way that it's required by design, we should also require the user to intentionally issue the command to match that. I wrote the instruction clearly in the docs.
Signed-off-by: vsoch <[email protected]>
|
Awesome! Please ping me for any issues or additional needs that might come up. Thanks for all the help! And a question for your team - I wanted to see if I could feature qpixel for the weekly software showcase that I run for the research software encyclopedia? E.g see https://rseng.github.io/rseng/blog/. It’s of particular interest to the research community because I know of several groups trying to create a community like this. |
|
That sounds great. Thanks for your work on this PR. |
|
Awesome! Are there any docs about background / history of the project, pictures, or anything in particular you'd like me to share? If not, I'll come up with my best effort for an introduction, rationale, and then sharing various links/ideas (akin to the others). |
|
Sharing with the research science encyclopedia sounds great, thanks! If you haven't seen our high-level vision yet, please take a look at https://meta.codidact.com/articles/276296. It's about where we're headed, not so much where we came from; I don't know if the latter is stated clearly anywhere. (Basically: unhappy users and moderators on Stack Exchange set out to build an alternative, then realized that communities are more than Q&A and we needed to think bigger. The focus is not on duplicating or competing with SE; SE was just the catalyst. By building a new thing we have the opportunity to apply lessons learned over the years on other platforms.) Or, I now see the comment from luap42 -- do that. :-) |
4 participants
This pull request will add a "docker" folder with contents to allow for a dockerized development deployment of QPixel. Notably, this initial version is done for development, and we have two ways to proceed:
One thing that I was thinking - it would be really useful if there was code to allow for any (or some subset) of config options to be grabbed in the environment. That way, the user could customize anything from the environment in Docker instead of having the check for
.dockerenv. Let me know your thoughts!This will close #70