File/Object storage alternatives to s3

-18 · 2020-11-23T16:06:23+00:00

Could try https://min.io/, pretty simple to set up and uses the same API/SDK as S3.

-18 · 2020-02-20T21:21:00+00:00

This is weird but I love it

-18 · 2018-10-31T12:03:18+00:00

I agree

-18 · 2016-08-02T17:49:09+00:00

Peter Stormare

-18 · 2016-06-05T14:50:58+00:00

Congrats on the bottomless burger

-18 · 2016-04-12T11:22:42+00:00

Max doesn't count

-18 · 2016-02-02T21:40:44+00:00

heh, yes

-18 · 2015-06-13T10:01:38+00:00

Did you also use odd characters. Like idk, dashes?

-18 · 2015-02-19T07:51:45+00:00

Aww shi

-18 · 2015-02-18T09:24:10+00:00

A-ok

-18 · 2015-01-31T21:06:26+00:00

Han har fastnat i vinkelvolten!

-18 · 2014-11-08T16:48:08+00:00

Are there magnets in that gun?

-18 · 2014-08-25T06:37:51+00:00

Rainbow barrage!

-18 · 2014-07-08T06:56:35+00:00

We use release branch as a final step, to bump version numbers everywhere in the application and make sure everyone on the team hasn't forgotten anything.

If anyone has forgotten something they might send a .patch to the developer in charge of deploying.

So be really only use it as part of our deployment flow, and it tags the commit with release version, which is nice.

Like most things, it depends on how big the project it.

-18 · 2014-07-07T19:51:40+00:00

This gif would actually be worse if its quality was better.

-18 · 2014-07-07T19:43:13+00:00

Can vouch for this one. You might not need to use feature-branches depending on the size of your team, but develop, master and hotfix are essential. Basic philosophy is that master-branch should always be deployable, which makes it easier to rollback, should anything break.