Setup a demo instance using the latest pre-release 0.1.2. The demo instance should be protected by some sort, maybe http-access? This instance is to show people we know / who are interested in our project (as a user oder developer) what the software can accomplish and to gather some feedback (actually very important)
Comment by @Commander1024 from Sun, 04 Oct 2020 19:26:42 CEST
## Original https://git.mowoe.com/reverend/lostplaces-backend/issues/28 by @reverend from Sat, 03 Oct 2020 12:13:02 CEST
Setup a demo instance using the latest pre-release 0.1.2. The demo instance should be protected by some sort, maybe http-access? This instance is to show people we know / who are interested in our project (as a user oder developer) what the software can accomplish and to gather some feedback (actually very important)
### Comment by @Commander1024 from Sun, 04 Oct 2020 19:26:42 CEST
Been there, done that: https://lostplaces.commander1024.de in production mode with testdata.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Original https://git.mowoe.com/reverend/lostplaces-backend/issues/28 by @reverend from Sat, 03 Oct 2020 12:13:02 CEST
Setup a demo instance using the latest pre-release 0.1.2. The demo instance should be protected by some sort, maybe http-access? This instance is to show people we know / who are interested in our project (as a user oder developer) what the software can accomplish and to gather some feedback (actually very important)
Comment by @Commander1024 from Sun, 04 Oct 2020 19:26:42 CEST
Been there, done that: https://lostplaces.commander1024.de in production mode with testdata.