[L2Ork-dev] Register before downloading?

[Jonathan Wilkes]

On Wed, Oct 21, 2020 at 10:36 AM Jonathan Wilkes <jon.w.wilkes at gmail.com> wrote:
>
> Ok, now I've completely reversed the problem:
>
> git.purrdata.net is completely public, but sign ups for new accounts
> have been turned off.
>
> Given that we have *way* fewer drive by merge requests than people
> downloading the software/cloning the repo, being stuck on *this*
> problem should be more tenable as we figure out what to do going
> forward.
>
> Let me know if anything else is awry and I'll revisit Gitlab's big
> collection of ambigiously labeled checkboxes.

This won't work at all-- it means nobody can sign up in order to report bugs!

Can someone think of a workaround to make our gitlab ce instance usable? I need:

1. snippets disabled, or at least not viewable without logging in
2. user profiles disabled, or at least not viewable without logging in
3. *only* git.purrdata.net/jwilkes/purr-data should be publicly
viewable without logging in. All other repos not viewable unless you
log in

That would restrict use/SEO spam to my own issue tracker (and I guess
merge requests) which is easily managed.

Can anyone think of a way to achieve this? Is there some clever custom
nginx setup to achieve this?

Unless we can solve this, there's no way to keep the repo accessible
and maintainable.

-Jonathan




>
> -Jonathan
>
> On Wed, Oct 21, 2020 at 10:06 AM Jonathan Wilkes <jon.w.wilkes at gmail.com> wrote:
> >
> > On Wed, Oct 21, 2020 at 9:33 AM Jonathan Wilkes <jon.w.wilkes at gmail.com> wrote:
> > >
> > > On Tue, Oct 20, 2020 at 11:04 PM Albert Graef <aggraef at gmail.com> wrote:
> > > >
> > > > On Tue, Oct 20, 2020 at 6:15 PM Jonathan Wilkes <jon.w.wilkes at gmail.com> wrote:
> > > >>
> > > >> I can update that page so it doesn't require a login. Where should
> > > >> those links point?
> > > >
> > > >
> > > > All of the links to https://git.purrdata.net/amorsi/purr-data presumably are broken. Also, the "Windows and OSX" link points to https://github.com/jonwwilkes/purr-data/releases which hasn't been updated in a while. The easiest thing would be to just have https://www.purrdata.net/ forward to https://agraef.github.io/purr-data/, which also has all the information and looks much prettier IMHO. ;-)
> > > >
> > > >> However, for cloning the repo we seem to be stuck with the login requirement.
> > > >
> > > >
> > > > Needing to register just to *clone* the source repo? That's insane. Did that come flying in with the most recent Gitlab update as well?
> >
> > I opened the instance up to public perusal. But this is not
> > maintainable-- spammers *will* begin registering bogus accounts,
> > creating spam repos, and indexing them on Google.
> >
> > The only option besides moving to github would be to keep the repo
> > public but restrict sign ups.
> >
> > We should probably figure out our course of action in the next few
> > days before the SEO spam becomes a problem again.
> >
> > -Jonathan
> >
> > > >
> > > >> If this is a problem our only course of action is to jettison Gitlab.
> > > >
> > > >
> > > > Or maybe downgrade to the previous Gitlab version which seemed to work a lot better?
> > >
> > > There are too many regular bug fixes to too many moving parts to make
> > > that feasible for a public-facing serving like Gitlab.
> > >
> > > I'll have another look for a workaround. But if there isn't one then
> > > these are our only options.
> > >
> > > -Jonathan
> > >
> > > >
> > > > Albert
> > > >
> > > >
> > > >> But that's a huge task and someone other than me would have to do all
> > > >> the boring infrastructure adjustments for issue tracker, CI/runners,
> > > >> etc.
> > > >>
> > > >> -Jonathan
> > > >>
> > > >> >
> > > >> > You can find proper information and get what you want on the GitHub mirror:
> > > >> >
> > > >> > https://agraef.github.io/purr-data/ (website)
> > > >> > https://github.com/agraef/purr-data/releases/tag/2.15.2 (latest release)
> > > >> > https://software.opensuse.org/download/package?package=purr-data&project=home%3Aaggraef (OBS packages)
> > > >> > https://github.com/agraef/purr-data/wiki/Installation#linux (detailed Linux installation instructions)
> > > >> >
> > > >> > HTH,
> > > >> > Albert
> > > >> >
> > > >> >
> > > >> > On Tue, Oct 20, 2020 at 4:55 PM Antonio Roberts <antonio at hellocatfood.com> wrote:
> > > >> >>
> > > >> >> I'm attempting to download Purr Data for Ubuntu but when I click on
> > > >> >> the download links in this website https://www.purrdata.net/ it asks
> > > >> >> me to register first. Is this a bug? Can I download without
> > > >> >> registering first?
> > > >> >>
> > > >> >> Kind regards,
> > > >> >>
> > > >> >> Antonio
> > > >> >>
> > > >> >> --
> > > >> >> ============================
> > > >> >> antonio at hellocatfood.com
> > > >> >> http://www.hellocatfood.com
> > > >> >> ============================
> > > >> >> _______________________________________________
> > > >> >> L2Ork-dev mailing list
> > > >> >> L2Ork-dev at disis.music.vt.edu
> > > >> >> https://disis.music.vt.edu/listinfo/l2ork-dev
> > > >> >
> > > >> >
> > > >> >
> > > >> > --
> > > >> > Dr. Albert Gr"af
> > > >> > Computer Music Research Group, JGU Mainz, Germany
> > > >> > Email: aggraef at gmail.com, web: https://agraef.github.io/
> > > >> > _______________________________________________
> > > >> > L2Ork-dev mailing list
> > > >> > L2Ork-dev at disis.music.vt.edu
> > > >> > https://disis.music.vt.edu/listinfo/l2ork-dev
> > > >> _______________________________________________
> > > >> L2Ork-dev mailing list
> > > >> L2Ork-dev at disis.music.vt.edu
> > > >> https://disis.music.vt.edu/listinfo/l2ork-dev
> > > >
> > > >
> > > >
> > > > --
> > > > Dr. Albert Gr"af
> > > > Computer Music Research Group, JGU Mainz, Germany
> > > > Email: aggraef at gmail.com, web: https://agraef.github.io/
> > > > _______________________________________________
> > > > L2Ork-dev mailing list
> > > > L2Ork-dev at disis.music.vt.edu
> > > > https://disis.music.vt.edu/listinfo/l2ork-dev