New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Move homepage and repository #453

Closed
FloEdelmann opened this Issue Mar 26, 2018 · 17 comments

Comments

Projects
None yet
4 participants
@FloEdelmann
Copy link
Member

FloEdelmann commented Mar 26, 2018

Heroku allows us to use 550 free dyno hours per month. It looks like this is not sufficient anymore since OFL is gaining some interest! 😊
Unfortunately, this results in the website being not accessible for roughly a week per month – which is not quite optimal.

We should move to a different Hosting provider with a new domain (like open-fixture-library.org instead of open-fixture-library.herokuapp.com).

It might be good to move the GitHub repo to its individual organization at the same time. That could allow finer access control mechanisms for contributors, while having to update links anyway. @peternewman, could you give any advice if this is the right thing to do and maybe have any tips for the moving process?

@peternewman

This comment has been minimized.

Copy link
Member

peternewman commented Mar 26, 2018

Hi @FloEdelmann

I'm kind of surprised you're going through 18 hours a day, but I don't really know how their charging works.

I was going to suggest going to a GitHub org at some point anyway. There's some notes on moving repos here:
https://help.github.com/articles/transferring-a-repository/

But essentially create an organisation, then move it in. I think if you don't make a fork (or fork with a slightly different name, it should keep redirecting from where it is now, to the new repo.

The org should also make it easier for you and @fxedel to collaborate, as all work can be done in PRs, rather than branches of the main repo.

We've migrated one or two bits into @OpenLightingProject in the past with no real issues.

@peternewman

This comment has been minimized.

Copy link
Member

peternewman commented Mar 26, 2018

Why not make the org now, then you can play with the permissions stuff etc with a test repo, before you do the migration.

@peternewman

This comment has been minimized.

Copy link
Member

peternewman commented Mar 26, 2018

One option, if you're interested @FloEdelmann / @fxedel would be to come under the @OpenLightingProject umbrella (like a mini version of freedesktop or Apache). We could give you full admin rights on your repo (and any others you wanted/needed to add down the line). Plus you wouldn't need to think of a good org name. πŸ˜€

@FloEdelmann

This comment has been minimized.

Copy link
Member Author

FloEdelmann commented Mar 27, 2018

@peternewman Thanks for your insights! It's good to hear that you have already done it without real issues in the past.

I don't know about you @fxedel, but I think it'd be awesome for OFL to be part of the Open Lighting Project! 😊
Possibly that also attracts some more people to the project.

We've bought a vServer yesterday, so I'll play with website migration / auto deployment today.

@fxedel

This comment has been minimized.

Copy link
Member

fxedel commented Mar 27, 2018

I'd be very pleased to contribute under the flag of the Open Lighting Project πŸ‘

Creating a test repository and playing around with permissions there before migrating OFL seems to be a good idea, though.

@peternewman

This comment has been minimized.

Copy link
Member

peternewman commented Mar 27, 2018

Okay great!

If I've pressed the right buttons, you should be able to create a test repo now @FloEdelmann , do you want to give that a go and let me know? @fxedel I've invited you to the org too.

I imagine we might be able to offer a suitable subdomain off openlighting.org too, e.g. fixtures.openlighting.org or ofl.openlighting.org ?

@FloEdelmann

This comment has been minimized.

Copy link
Member Author

FloEdelmann commented Mar 27, 2018

Looks like it works! I can create repos (https://github.com/OpenLightingProject/ofl-test) and edit its settings, including team management.

It's really an honor to now be part of the Open Lighting Project! Thank you a lot @peternewman! πŸŽ‰

I've actually already bought the open-fixture-library.org domain and would like to use it as the primary domain. Maybe one could set up a redirect from one of the domains you mentioned, but I don't see an advantage if we don't actively use it.

On our new server (as mentioned, https://open-fixture-library.org/), you will be able to sometimes see something and sometimes not, because I am still playing around with the setup. To get to the current state was actually easier than expected πŸ˜„

@FloEdelmann

This comment has been minimized.

Copy link
Member Author

FloEdelmann commented Mar 28, 2018

The website is now moved to open-fixture-library.org without any major problems! (see #456)

On Heroku, I manually pushed a new version that redirects every request to the new URL. We'll see if that works on April 1st, but I am optimistic.

I also transferred the repo to OpenLightingProject (as you can see πŸ˜‰), but unfortunately locked myself out πŸ˜…

At the open-fixture-library-owners's repositories page, you can see that the team has read access instead of admin access (I could only select a team during the transition – not its role).

screenshot_2018-03-28_19-45-58

@peternewman Do you have the privileges to change that? Otherwise, I'll contact the GitHub support.

Until then, neither @fxedel, myself, nor the fixture editor (which uses a personal access token of mine) will be able to push.

@peternewman

This comment has been minimized.

Copy link
Member

peternewman commented Mar 28, 2018

I think that's sorted now @FloEdelmann . Does it work for you?

@FloEdelmann

This comment has been minimized.

Copy link
Member Author

FloEdelmann commented Mar 28, 2018

Thanks @peternewman, looks good now! πŸŽ‰

Things we have to do now:

  • Update all links to the old repo in the code
  • Update links to the old website / repo from other places we have access to
  • Tell Google about the moving (not possible until April 1st, when the redirect is active)
  • Update history in About page
  • Increase schema version and package.json version
@peternewman

This comment has been minimized.

Copy link
Member

peternewman commented Mar 28, 2018

Well see #457 for the first thing.

Also OpenLightingProject/rdm-app#180 for the rdm-app one.

What do you want package.json bumped to 0.3.0 or 0.2.1? Likewise with the schema?

@FloEdelmann

This comment has been minimized.

Copy link
Member Author

FloEdelmann commented Mar 28, 2018

Ah sorry, I directly commented at #457 for the version numbers.

@FloEdelmann

This comment has been minimized.

Copy link
Member Author

FloEdelmann commented Mar 29, 2018

@peternewman One more thing: We've used Greenkeeper so far to keep npm packages up-to-date. It checks in-range updates if they pass our tests and creates pull requests for major version changes (see e.g. #435 and #448).

Since the migration, it is no longer active, as it has to be granted organization access (see greenkeeperio/greenkeeper#420). Would you mind doing this for us?

@peternewman

This comment has been minimized.

Copy link
Member

peternewman commented Mar 29, 2018

Done against the two OFL repos.

@espy

This comment has been minimized.

Copy link

espy commented Apr 3, 2018

Hi everyone, Alex from Greenkeeper here. Your enabling of https://github.com/OpenLightingProject/open-fixture-library was somehow lost between GitHub and Greenkeeper, sorry about that. I’ve marked the repo as enabled and reset it, and since all dependencies seem to be up to date, it’s now just directly enabled, without the usual initial PR. The badge also reflects this now.

Everything should work as expected now, please get in touch if not.
Thanks!

πŸ€– 🌴

@FloEdelmann

This comment has been minimized.

Copy link
Member Author

FloEdelmann commented Apr 5, 2018

All points in my comment above are now resolved, so the transition is finally complete! πŸŽ‰

Thanks again to everyone who helped making it possible! πŸ‘

@FloEdelmann FloEdelmann closed this Apr 5, 2018

@peternewman

This comment has been minimized.

Copy link
Member

peternewman commented Apr 11, 2018

Your redirect seems to be working.

@espy not quite sure what happened, but probably my fault, trying to just enable Greenkeeper for that one repo rather than the whole org.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment