GodotBeginnerRich Completely unnecessary, not ok!

GodotBeginnerRich Reported, sit down, the Mods won't do anything

See this as a warning @GodotBeginnerRich . If you try this again, you will get suspended!

Toxe If this wasn't what you were asking for then ask better questions.

Please, mind your tone. Unnecessary comment.

  • Toxe replied to this.

    MikeCL Please, mind your tone. Unnecessary comment.

    I just replied in the same tone as "please learn to read". But you are right.

    If it's for size constraints bitbucket has (practically) unlimited file size (the max per file is 1 gig which is huge for a singular asset), I've been using it for a while and it's great

      5 months later

      TH3-S4LM0N 1gib per file is not huge, blend file with high poly model can blow up to several gibs.

      I suggest OP to get yourself a minipc, and start hosting gitea. Gitlab for one person is too (complicated) and resource intensive. Gitlab needs 4 gib ram, while gitea runs on 100mb ram.

      I switched from gitlab to gitea (self hosted) and never looked back.

      Unlimited space, unlimited repos, commit what you want. No redditors to ban/mute/report you.

        kuligs2 1gib per file is not huge, blend file with high poly model can blow up to several gibs.

        If you are keeping your highpoly/raw assets in your code repo then you are probably doing it wrong.

          Megalomaniak If you are keeping your highpoly/raw assets in your code repo then you are probably doing it wrong.

          Personally, I have a hard time accepting the concept of separating code and resources. It is preferable to have everything related to the project stored in one place.

          Compartmentailization has it's perks, but I didn't mean that you shouldn't keep your game ready assets with the code. I said RAW assets. The art department should have their own centralized asset management pipeline and it'll involve software better suited to them. Using something like git or perforce for it would be silly.

            Megalomaniak I said RAW assets. The art department should have their own centralized asset management pipeline and it'll involve software better suited to them. Using something like git or perforce for it would be silly.

            I'm not sure that wanting to keep everything related to a project in one place can be called "silly".

            And the desire to put "raw assets" in a common archive is understandable. But what does this have to do with software? They're just being stored.

            "Inappropriate" would probably be a more correct definition. But then what is appropriate?

            Megalomaniak First of all, i dont own no company with multiple departments. Im just 1 person. So im gonna use whatever makes senese to me, and whatever works.

            There is no better way for version control than git, other than keeping nuclear version copies of files at set intervals.

            If its wrong then enlighten us with your professional experience, on how to do is RIGHT

            Btw quick search says this

            If you are a single indie developer or even a small house(~10 or less people) then of course you can make anything work, but then the question seem almost irrelevant. I was answering from the perspective of running a production house with multiple departments where the art pipeline would be a separate department. I honestly thought that was obvious from my comment, but fair enough, my bad. I should have been clear about that. As for some examples that come to mind:

            https://openassetio.github.io/OpenAssetIO/
            https://www.foundry.com/products/katana

            Mind, Katana is specifically for look dev and lighting for vfx, but I linked it since it is non-the less relevant as the other link there is to a cross industry effort to create a standard API for Digital Asset Management(or DAM for short) platforms which cites it as the inspiration. Bigger studios currently tend to roll their own custom solutions.

            Blender's asset manager is supposed to be developed with OAio in mind, btw. It's been a while since I last followed the development of that though, so I don't know if they've changed their minds on it since then.

            Other cool things potentially worth keeping an eye on, maybe:
            https://www.aswf.io/projects/

              Megalomaniak As for some examples that come to mind:

              https://openassetio.github.io/OpenAssetIO/

              The OpenAssetIO release version is currently in a beta stage

              It's not an area where it's desirable to use a not very stable version.

              Paid. Hard to call cheap.

              They use GitHub themselves.

              I was answering from the perspective of running a production house with multiple departments where the art pipeline would be a separate department.

              Well I assumed we were discussing the question from the thread title in a practical area. Clearly something from the life of an indie developer. And not much deviation all the time.

              Misunderstandings are commonplace.

              kuligs2 I suggest OP to get yourself a minipc, and start hosting gitea.

              Probably the most interesting option. And the possibility to transfer from Gitea to GitLab if necessary. Maybe I'll have questions about it. Especially since I have a free comp for it. Although the old computer meets even the requirements of GitLab more than enough.

              • What is the difference between Gitea and Forgejo? Except that the latter doesn't have a Win version.
              • What are some good Gitea manuals out there?

                Tomcat What is the difference between Gitea and Forgejo? Except that the latter doesn't have a Win version.
                What are some good Gitea manuals out there?

                Honestly i just use them "git-servers" on a very surface level. Create repo, commit, push, sometimes banch out and merge. I dont use any of them fancy features. Just from my personal experience, gitlab was a drag to maintain, you need to update it constantly becasue they often break inter-version migrations, so you need to upgrade often or if you upgrade later then in sequence, wich is a drag. Also gitlab used up 4gb of ram at minimum. I had other services that had to be run, so the ram space was something that i considered.

                Migration between gitlab-gitea, was doable but using some shady scripts. But a messy thing.

                One thing on gitea i couldn't get working (lack of knowledge i guess, even tho i did exactly just the way others did from tutorials/documentation) was to get ssh working. Cloning and pushing via ssh instead of https.

                On gitlab everything was working out of the box.

                Overall gitea covers all my needs for foreseeable future. Ofc keep backups and backups of backups.

                Gitea the one i run, runs in docker, so the data it generates is easily manageable/movable.
                Gitbal was a whole VM, and data was all over the place so backing up was not something i did because i didnt want to sift through docs and learn more linux stuff just to copy data...

                And that forge thing https://forgejo.org/compare-to-gitea/ seems like i will have to switch once again 😃. Thanks for the info. Forge is free while gitea is under the umbrella corps.

                  kuligs2 Honestly i just use them "git-servers" on a very surface level.

                  That's what I need to do now — start out from simple.

                  Also gitlab used up 4gb of ram at minimum.

                  This is the easiest question — I have 12GB of RAM on my old computer. How much is on the new one, I'd rather not say (or I'll be lynched here).

                  Cloning and pushing via ssh instead of https.

                  How important is that?

                  while gitea is under the umbrella corps.

                  What are the problems that follow from that? I work on Win 11, and they don't provide this version of Forgejo, apparently as a matter of principle.

                    Tomcat It's not an area where it's desirable to use a not very stable version.

                    It's in beta, but that doesn't mean the software is necessarily unstable. It'll probably be in 'beta' for another 5 to 10 years while they still add new APIs to the standard and such, maybe change a few of them. So the API isn't stable yet, sure. But it is usable.

                    Tomcat Paid. Hard to call cheap.

                    It was just an example of what a DAM is. Not a recommendation for one.

                    Tomcat They use GitHub themselves.

                    For code hosting, sure. That was never under debate.

                    Tomcat Well I assumed we were discussing the question from the thread title in a practical area.

                    Pretty sure that discussion ended in 2023.11.21.

                    kuligs2 I suggest OP to get yourself a minipc, and start hosting gitea.

                    Tomcat Probably the most interesting option.

                    I definitely can agree that it's a good idea to set up a home server running linux with a journaling file system. Then install gitaea or gitlab on it for code hosting too. But unlike a DAM git won't manage file metadata such as tags or copyright info per file. Also for backups you can use timeshift or the like along with all the caching the file systems journaling brings you. Don't forget to have pairs of identical drives and use software RAID 1 for data mirroring.

                      Megalomaniak I definitely can agree that it's a good idea to set up a home server running linux with a journaling file system.

                      Linux, exactly? 🙁

                      Pretty sure that discussion ended in 2023.11.21.

                      I was sure the discussion was ongoing. For another question — should have opened another thread.

                      The reply from Wednesday, April 17, 2024 was exactly to the previous post.

                      Misunderstandings are commonplace. ©️

                      But unlike a DAM git won't manage file metadata such as tags or copyright info per file.

                      It would be useful, but for now the absence is not critical.

                      Don't forget to have pairs of identical drives and use software RAID 1 for data mirroring.

                      Right now I have the disks in RAID 0. 🚀 But will put it in the plans.

                        Tomcat Linux, exactly? 🙁

                        You could use BSD, but I'd rather have an easier time with a GUI environment, at which point if you aren't going with a highly specialized headless setup you might as well go linux over BSD.

                          Megalomaniak you might as well go linux over BSD.

                          Gitea has a version for Win. I have a complicated relationship with Linux. It is in my plans to try it out… once again… but that's a long shot.

                          Don't forget to have pairs of identical drives and use software RAID 1 for data mirroring.

                          If one slides into heavy offtopic, it's a controversial proposition.

                          «Identical drives» — they may sprinkle the same way (at the same time). Remember the DTLA story? There is a confession recommending to use not only different models, but even from different companies.

                          «RAID 1» — after replacing a failed drives, RAID copying starts, which increases the load on the working drives. And if it fails… RAID 10 looks preferable, but expensive. RAID 5 is a bit cheaper in terms of drives and more interesting, but the key for it is expensive. I don't know if it is possible to implement it on Linux.

                          However, RAID 0 requires exactly the identical drives.

                          I'd just recommend identical drives because they will perform about the same. So one won't hold the other back. But realistically same capacity should suffice. Yes there's more complex RAID schemes. But if you are using something like rsync and backing up the image on another device, preferably offsite even perhaps... then RAID 1 should suffice.

                          As for homeservers, i have a dedicated minipc that is sub 35W on load, mostly idle and i use proxmox on it for host OS and for any other service that i need i just use debian image and create container (not a vm). And there i just host docker and just use it as normal.. Can install gitea that way and use it. It took me little over a year to master using proxmox. IMO its the best. Because you can back up your containers/VM's as is and even if your host gets nuked (happened to me once) you can restore it with few clicks in web GUI.

                          Tomcat

                          Tomcat Cloning and pushing via ssh instead of https.

                          How important is that?

                          Well its more secure if you do it from outside your LAN, ssh, maybe faster in some cases . I work from multiple locations, so its better to be safe, someone is definitely sniffing network packets these days.

                          But if you also run VPN on your homeserver then it dont matter, you can just connect to VPN and connection is already encrypted so no worries there.
                          Im no genius, just a surface level user.

                          Tomcat while gitea is under the umbrella corps.

                          What are the problems that follow from that? I work on Win 11, and they don't provide this version of Forgejo, apparently as a matter of principle.

                          Like with everything, privacy is holy. Corporations will server you ads, will selll your data, will force you to update etc.etc.

                          Free software is free. You can do what you want. If it works then its great, if it dont work you can fix it yourself.

                          Yesterday i moved my gitea data to that forgejo thing, was 2 min job. They even have documentation how to migrate. Everything works as it did before, no problem.