• 8 Posts
  • 99 Comments
Joined 1 year ago
cake
Cake day: June 27th, 2023

help-circle
  • I was under the impression that Google retired the “app password” workflow and moved to Gmail API within Google Cloud. I have the API set up and that’s what I’m using in the Vikunja configs but like I mentioned in the post, at this point I don’t care if its Gmail or something else. I just need the email functionality to work so I will use whatever service works well with Vikunja.







  • Not quiet. I was running gitea before so my mount was ./gitea:/data but since switching over to forgejo, I renamed my ./gitea directory to ./forgejo. Adjusted my compose file to have a mount of ./forgejo:/data.

    Now inside of that renamed forgejo directory, there are a bunch of gitea references and even one more directory called gitea. When I migrated everything worked right away but since I wanted a cleaner transition, I renamed and switched all gitea references to forgejo but went I brought the stack back online, it went belly up.

    As a troubleshooting step, I recreated my compose file and created a new empty ./forgejo on a different machine just to see what a new and fresh install would look like and the forgejo stack itself created all kinds of gitea references and gitea directory once I brought it up. So to fix my original deployment, I reverted all the references back from forgejo to gitea and everything worked again.

    For fun, I went out to codeberg to look at the Dockerfile and saw that they had a bunch of gitea things within their own Dockerfile so nothing I can do for now










  • lal309@lemmy.worldtoSelfhosted@lemmy.worldAssistance migrating from gitea to forgejo
    link
    fedilink
    English
    arrow-up
    0
    arrow-down
    1
    ·
    edit-2
    7 months ago

    Okay so your post inspired me to make the switch. All I had to do was switch out the image to the forgejo one. Everything worked right away. To try to make things as clean as possible, I went ahead and renamed my bind volume paths and app.ini stuff from gitea to forgejo but no matter what I tried, once I started the container, the container would create a gitea directory with a new app.ini. I even tried to run the forgejo compose on another host and the app still creates a gitea directory within the bind mount. Am I doing something wrong. I understand it’s a drop in replacement but I’m sure there’s a way to get a cleaner cut over.

    compose.yml

    volumes:

    • ./data:/data

    Host directories

    ~/forgejo

    • data - forgejo - renamed for the migration - git - ssh - gitea - gets created by the app no matter what I do or what paths are set in app.ini
    • compose.yml

    How do I keep forgejo from creating this gitea directory? Why doesn’t it create a forgejo directory???

    Edit: gitea version was - 1.21.7 and forgejo replacement image is 1.21.7-0






  • Copy/paste from another comment

    “Just to be clear I just need to track my sales/revenue (even if input is manual) and track expenses (bonus if I could upload a picture of a receipt).

    I don’t need to actually send an invoice (I do this straight from my website and it’s a seamless integration so not looking to reinvent this wheel, yet!)

    Given the above, is in InvoiceNinja still a good candidate?”