🛠️ `Neighborhood`: `Contributors` can use `DevContainers` and `Codespaces`

[KellyAH]

• https://github.com/zinc-collective/convene/issues/892

Convene's DevContainer streamlines the contributor experience by:

• Allowing anyone with a Github account to contribute using a Codespace
• Provide a "clean" developer environment without requiring Contributors to modify their local environment

Known Issues

Could not open directory "pg_logical/snapshots": Permission denied

convene-db-1     | 2023-05-04 02:08:31.233 UTC [60] LOG:  checkpoint starting: time
convene-db-1     | 2023-05-04 02:08:31.233 UTC [60] ERROR:  could not open directory "pg_logical/snapshots": Permission denied

Current Workaround

When my CodeSpace was in this state, I was able to run docker-compose down and then ./.devcontainer/startup.bash and it initialized correctly.

Why it wouldn't do this correctly upon the first starup/attach, I don't know... It almost seems to be some race condition between the database container startup and some user startup in the surrounding devcontainer, but I'll have to look into it more at some point.

[daltonrpruitt]

Current Workaround

When my CodeSpace was in this state, I was able to run docker-compose down and then ./.devcontainer/startup.bash and it initialized correctly.

Why it wouldn't do this correctly upon the first starup/attach, I don't know... It almost seems to be some race condition between the database container startup and some user startup in the surrounding devcontainer, but I'll have to look into it more at some point.

[daltonrpruitt]

Forked repos cannot use the devcontainer due to it being private to the organization. Should be able to fix by making it either public or somehow linked to forked repos. Needs further investigation and/or testing. Any thoughts on these options? @zspencer

[zspencer]

@daltonrpruitt - Nice catch! I've made it public.

[KellyAH]

Darn I keep encountering a variation of this issue where permission is denied to a specific file. Thanks @daltonrpruitt for the workaround to get me unstuck.

I just spun up a fresh code space instance on my feature branch https://github.com/zinc-collective/convene/pull/1602 and hit this error loading the front end.

[daltonrpruitt]

Hmm. I am annoyed the fresh CodeSpace instances aren't working suddenly for some reason. I will have to look into this later. Thank you for the info!

[KellyAH]

Thanks so much for all your hard work on improving the code spaces @daltonrpruitt! ❤️ It's been a huge help when my local dev enviro gets messed up. It feels great knowing I can use code spaces as my primary or back up dev enviro/coding space.

[zspencer]

Glad you were able to find a workaround; bummer that our current codespaces are a touch brittle but I'm glad we're using them and learning how to debrittle them!!!