Kissaki

joined 1 year ago
[–] Kissaki@programming.dev 2 points 2 weeks ago (2 children)

2FA? But it said "with one click". So that's not true?

[–] Kissaki@programming.dev 12 points 3 weeks ago

Being able to build the app as you are trying to do here is an issue we plan to resolve and is merely a bug.

[–] Kissaki@programming.dev 14 points 3 weeks ago (2 children)

So it really is that simple: a small bash script, building locally, rsync'ing the changes, and restarting the service. It's just the bare essentials of a deployment. That's how I deploy in 10 seconds.

I'm strongly opposed to local builds on any semi-important or semi-complex production product or system.

Tagged CI release builds give you a lot of important guarantees involved in release concerns.

I'll take the fresh checkout and release build time cost for those consistency and versioned source state guarantees.

[–] Kissaki@programming.dev 10 points 3 weeks ago

learned from 10 years/millions of users in production

10 years per millions of users is an interesting metric :P

[–] Kissaki@programming.dev 1 points 3 weeks ago* (last edited 3 weeks ago)

I wasn't aware the GitHub terms of service explicitly grant / require you to grant permission to fork [within GitHub].

GitHub ToS section License Grant to Other Users

By setting your repositories to be viewed publicly, you agree to allow others to view and "fork" your repositories (this means that others may make their own copies of Content from your repositories in repositories they control).

If you set your pages and repositories to be viewed publicly, you grant each User of GitHub a nonexclusive, worldwide license to use, display, and perform Your Content through the GitHub Service and to reproduce Your Content solely on GitHub as permitted through GitHub's functionality (for example, through forking). […] If you are uploading Content you did not create or own, you are responsible for ensuring that the Content you upload is licensed under terms that grant these permissions to other GitHub Users.

[–] Kissaki@programming.dev 16 points 3 weeks ago* (last edited 3 weeks ago)

It's been over 10 years since we released Rogue Legacy 1, and in the pursuit of sharing knowledge, we are officially releasing the source code to the public.

https://github.com/flibitijibibo/RogueLegacy1/

License head

Rogue Legacy 1's source code is made available under a custom license. Basically, you can compile yourself a copy, for free, for personal use. But if you want to distribute a compiled version of the game, you might need permission first. See the EXCEPTIONS.md page for more information.

[–] Kissaki@programming.dev 1 points 4 weeks ago

Yeah, I thought the same. Pretty bad name.

[–] Kissaki@programming.dev 9 points 4 weeks ago

Maybe all bunnies are actually snails with a fur coat on.

[–] Kissaki@programming.dev 10 points 4 weeks ago

Damn, such cute mascot pics, great work on that!

[–] Kissaki@programming.dev 3 points 4 weeks ago* (last edited 4 weeks ago)

I would like to see TS as the first class citizen however, with JS being deprecated essentially.

What do you mean by that.

From what I read, Deno does primarily use and target TS. They label all that JS stuff as backwards-compatibility and ability for a migration path.

view more: ‹ prev next ›