Recent

Author Topic: Using FPC domain for Gitlab  (Read 421 times)

Okoba

  • Sr. Member
  • ****
  • Posts: 392
Using FPC domain for Gitlab
« on: March 18, 2023, 06:10:11 pm »
Hello,

I guess this is already an examined case, but I wanted to make sure, as many services, even open ones like GitLab or Docker, are changing and limiting many free features even for open source projects.
I would like to suggest that instead of using the GitLab domain, it may be better to use the FPC domain. This way, if in the future the team chooses to move to a self hosted GitLab version, the posts, links, and many messages will continue to work.

Please feel free to ignore, if this is not possible or not needed.

Bi0T1N

  • Jr. Member
  • **
  • Posts: 81
Re: Using FPC domain for Gitlab
« Reply #1 on: March 18, 2023, 08:58:01 pm »
I guess this is already an examined case, but I wanted to make sure, as many services, even open ones like GitLab or Docker, are changing and limiting many free features even for open source projects.
I haven't read anything about GitLab wanting to restrict their program for open source projects. If they do, there are enough other places (smaller and larger ones) so that it would be counterproductive for them because less new employees will be familiar with the UI of GitLab (=less companies deciding for it).
Docker still has its sponsor program for open source so we just need to hope that they accept our application ;)
If not, there is still the GitLab registry and probably some others. :P

Okoba

  • Sr. Member
  • ****
  • Posts: 392
Re: Using FPC domain for Gitlab
« Reply #2 on: March 19, 2023, 08:52:50 am »
That was not my point. My point was, using FPC domain for repositories, so later on IF, anything changed, all these posts, don't get deprecated.

ccrause

  • Hero Member
  • *****
  • Posts: 705
Re: Using FPC domain for Gitlab
« Reply #3 on: March 19, 2023, 11:35:35 am »
I haven't read anything about GitLab wanting to restrict their program for open source projects. If they do, there are enough other places (smaller and larger ones) so that it would be counterproductive for them because less new employees will be familiar with the UI of GitLab (=less companies deciding for it).
Well, my fork of FPC source is no longer updated automatically by Gitlab, here is the message I received:
Quote
Your project is no longer receiving GitLab Ultimate benefits as of 2022-07-01. As notified in-app previously, public open source projects on the Free tier can apply to the GitLab for Open Source Program to receive GitLab Ultimate benefits. Please refer to the FAQ for more details.
More hoops to jump through.  But this is just a personal inconvenience which can be handled by running a git command on my local git clone to sync between upstream and my fork.

marcov

  • Administrator
  • Hero Member
  • *
  • Posts: 10569
  • FPC developer.
Re: Using FPC domain for Gitlab
« Reply #4 on: March 19, 2023, 11:46:05 am »
If a new gitlab instance is set up, while the hashes might remain the same, things like projectid etc might change, invalidating URLs

Okoba

  • Sr. Member
  • ****
  • Posts: 392
Re: Using FPC domain for Gitlab
« Reply #5 on: March 19, 2023, 11:58:06 am »
Thank you marcov for clarifying.

 

TinyPortal © 2005-2018