Demo login links result in DDOS protection triggered

[Zireael07]

No description provided.

[7yl4r]

I am seeing a 405 at the Hubble/Kepler "demo" links.

[Zireael07]

Yes, exactly, 405 with description saying it's ddos protection.

[7yl4r]

Oh, yes I see it now. I think the issue is that the current site is hosted on gh-pages and so the custom python server stuff we wrote are not handled.

We did an incomplete port because we didn't have any income to keep the server up.

Right now the project is in limbo awaiting revitalization.

[cwaddell]

What specs are needed?

…

On Mon, Sep 3, 2018 at 3:30 PM Tylar ***@***.***> wrote: Oh, yes I see it now. I think the issue is that the current site is hosted on gh-pages and so the custom python server stuff we wrote are not handled. We did an incomplete port because we didn't have any income to keep the server up. Right now the project is in limbo awaiting revitalization. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#111 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ACY_m2OXN79xLkoMYKnhHUUXYXAJ7IEFks5uXYNIgaJpZM4WX9D6> .

[7yl4r]

I think the basic application is light enough to run on a typical cloud providers' "small" instance or on commodity hardware.

Installation/setup is covered in INSTALL.md and INSTALL.py.

Those are pretty old though so just ask if you run into trouble.

[cwaddell]

I could host it as a semi-permanent place

…

On Tue, Sep 4, 2018 at 9:46 AM Tylar ***@***.***> wrote: I think the basic application is light enough to run on a typical cloud providers' "small" instance or on commodity hardware. Installation/setup is covered in INSTALL.md <https://github.com/rSimulate/Cosmosium/blob/master/INSTALL.md> and INSTALL.py <https://github.com/rSimulate/Cosmosium/blob/master/INSTALL.py> . Those are pretty old though so just ask if you run into trouble. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#111 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ACY_mwm7ZNbd-hCTSVLKUGjFqiIlFlRnks5uXoQ5gaJpZM4WX9D6> .

[7yl4r]

Sounds good to me.

I don't think we have any concrete plans for moving forward though; what do you think @iontom ?

[cwaddell]

Cool cool, I'll probably have time to set it up after work today.

…

On Tue, Sep 4, 2018 at 11:32 AM Tylar ***@***.***> wrote: Sounds good to me. I don't think we have any concrete plans for moving forward though; what do you think @iontom <https://github.com/iontom> ? — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#111 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ACY_m4kpI4WnupEzlKnSvVRms5aT4tQJks5uXp0LgaJpZM4WX9D6> .

[cwaddell]

Probably an issue with my setup, but it's stalling on the "repo.submodule_update()" line I have the correct version of the git module, digging into the installer seems that that is whats crapping out on me. Decided to forego figuring out the python git module, ran: git submodule init git submodule upgrade PyKEP error, probably something to do with Numpy. On Tue, Sep 4, 2018 at 11:50 AM Christopher Waddell < [email protected]> wrote:

…

Cool cool, I'll probably have time to set it up after work today. On Tue, Sep 4, 2018 at 11:32 AM Tylar ***@***.***> wrote: > Sounds good to me. > > I don't think we have any concrete plans for moving forward though; what > do you think @iontom <https://github.com/iontom> ? > > — > You are receiving this because you commented. > Reply to this email directly, view it on GitHub > <#111 (comment)>, > or mute the thread > <https://github.com/notifications/unsubscribe-auth/ACY_m4kpI4WnupEzlKnSvVRms5aT4tQJks5uXp0LgaJpZM4WX9D6> > . >

[BrianErikson]

I'm not sure why GitPython was statically versioned at 0.3.2.RC1 but removing that bit in 009390e seemed to solve the submodule issues in INSTALL.py.

For the PyKEP error, renaming from PyKEP on lines 4 & 7 in ./py/lib/traj/C3.py to from pykep solves it, and the application runs fine @ 46adb12. Give it another shot @cwaddell and let me know how it goes. Thanks for your interest in the project -- sorry that it hasn't had TLC in a while!

[7yl4r]

I'm not sure why GitPython was statically versioned at 0.3.2.RC1

Looks like I did that and I don't remember why. Probably a feature that was prerelease at the time. Still, I probably should have used >= though.

[BrianErikson]

No worries! Really it's a tough issue with projects like this (irregular maintenance) because PyKEP would've still ran into import errors with >= versioning. Dusting this off brought back a lot of good memories anyway :)