Manuel's Comments
-
-
Blog
- Waterhole 0.3
-
-
-
Blog
- Waterhole 0.3
I get errors on my local test instances after the update. I changed the requirement to 0.3 on two local instances, I don't get errors on the composer update, but when I try to access the sites I get database errors:
-
-
I'm a member at a freelancer cooperative and we offer some paid open-source products. The model we have is free for communities, paid for business. There is just one license and you always need a license key. But you can get a free one as a community user:
Well, just sharing our approach. What I believe would be important in general is finding a solution that promotes community contribution. You'll want to build a vibrant community around the product. Restricting size or customization options could work against that.
-
In any case, thanks for the suggestions :)
Not sure how this restriction to https works. But just getting started with Laravel..
-
Answer Ok, up now! Had to do two additional steps:
- manually add the link to static files in the public folder:
ln -s /home/forge/<your-sitename>/storage/app/public/ storage - add a SSL Certificate and then adjust APP_URL in the environment configuration to serve from https.
- manually add the link to static files in the public folder:
-
@Subarist Yeah, I don't think that's the right direction. It would also be weird if I'd need to access the server console to correct folder permissions when I use Forge to set them up correctly in the first place.
Thank you @Adeala Ademola! I guess that's also related to using Apache though.
The site is served from the public folder, so the folder is accessible and all. The issue I see is that the symlink
storage -> /storage/app/publicis not generated in the public folder. And when I add it manually, it's not used. -
Thanks for the suggestion @Subarist! I saw your previous post, but this relates to a setup with Apache, no?
-
-
Lounge
- Introduce Yourself 👋
I'm Manuel, from the Canary Islands
I've been working as a freelance community designer for the past two years now, with all my production projects based on Discourse. I'm excited to try my hands at Waterhole, it looks well-thought-out and fun to customize.
Kudos and congrats on the launch!
-
Yeah I had included these commands already. I actually dropped all tables with a migrate:fresh as well, as it's just test installations. But I still get the errors. Not sure how I can further investigate what's going wrong?