https://forum.cloudron.io/topic/12472/please-use-this-template-to-make-an-app-wishlist-request

@zonzonzon said in briefer - run SQL and Python, and turn notebooks into dashboards: @LoudLemur . Thank you for updating the topic. Hey, thanks for using the template. Your application request looks beautiful!

Thank you @girish And sure! Well, I'm not really good in inventing names, but I personally like animals such as foxes and ravens that are both cute and clever. And I figured to give the project a more unique name I looked up botany or gardening related names in various languages. I ended up with hortus as the word for garden in latin and combined them and was quite satisfied with the "look and feel" of the name.

I'm too interested. I need something simple and git feels very complicated and provides a messy ux for simple things and errors. Fossil was advised to me and i'd like to try

As of August 2024, it looks like notesnook now has a sync server that can be self-hosted. According to their roadmap, they've completed 3 of 4 steps to allow self-hosting, although the fourth is 'just' documentation. The last time I tried notesnook I thought the interface was great. Would love to try it with a self hosted sync server.

Great, and thanks for using the template!

@subven are you still running those bridges? I’m interested in picking this up for myself again

+1 for Akkoma. I just love it. Have been running it on a separate VPS for over a year now.

@igaudette If you would like to propose any of these for Cloudron, you should create individual App Requests for the ones you want, rather than lumping them in together.

Here is an ai generated list of potential solutions to some possible hurdles packaging molly brown: Here's the tidied section presented as a markdown code block: Potential Problems and Solutions Golang Version Compatibility Problem: Molly Brown requires specific Golang version compatibility. Solution: Specify the exact Golang version in the Dockerfile and ensure it's compatible with both Molly Brown and Cloudron. Configuration Management Problem: Managing configurations for different Cloudron environments. Solution: Use environment variables in CloudronManifest.json and modify the start script to generate a config file based on these variables. Persistent Storage Problem: Ensuring persistent storage for Gemini content. Solution: Define a volume in CloudronManifest.json for storing Gemini content, ensuring it persists across app updates and restarts. SSL/TLS Certificate Management Problem: Managing SSL/TLS certificates for the Gemini protocol. Solution: Utilize Cloudron's built-in SSL management if possible, or implement a custom solution in the start script to generate and renew certificates. Preserving Custom Configurations Problem: Updating Molly Brown without losing custom configurations. Solution: Store custom configurations in a separate volume and implement a migration script that runs during updates. Resource Allocation Problem: Efficient resource allocation in shared Cloudron environments. Solution: Carefully define resource limits in CloudronManifest.json and optimize Molly Brown's configuration for efficiency. Logging and Monitoring Problem: Integrating logging and monitoring with Cloudron. Solution: Configure Molly Brown to output logs in a format compatible with Cloudron's logging system, possibly using a log forwarding solution. Backup and Restore Problem: Ensuring comprehensive backup and restore functionality. Solution: Clearly define all data that needs to be backed up in CloudronManifest.json and thoroughly test the backup/restore process.

Sorry to ask, but how can i install this tool? In a LAMP App?

@marylou said in Feedly: https://github.com/feedly https://forum.cloudron.io/topic/12472/please-use-this-template-to-make-an-app-wishlist-request

I second this! Would like to see this in Cloudron as well! Others have run Trac/SVN in docker containers before, but no one seems to be maintaining them.

I am unable to upvote the original request due to a lack of reputation, but I would if I could. It is good to specify that in the time since this original request, the nurdism repo is archived, while m1k1o's fork is actively maintained. It would be very appropriate to add https://github.com/m1k1o/neko-rooms at the same time.