Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
hakre
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
21 ms
·
211.
▲
by
hakre
6y ago
you mean syncing to git bares on CI-nodes and then in the build not using a WAN remote but just clone from the bare with hard-links and checkout?
212.
▲
by
hakre
6y ago
Who says there is only one version field?
213.
▲
by
hakre
6y ago
Yes, for sure it is. But what is the alternative? A compiler can only complain on a monolith, it can't scratch boundaries out of the system it compiles (and still within that monolith, encapsulated system the data might be inconsistent
214.
▲
by
hakre
6y ago
Yes, personally I'm (generally) against version fields, however in the OPs meaning as I read it, if you add the version field it breaks the value (the version field invalidates value comparison for equality) and therefore will end up a
215.
▲
by
hakre
6y ago
The author argues DO is in favour to reduce complexity, but also notes on the prices of it and reminds that it's in the eye of the beholder to decide whether or not it is of benefit. Many of the early PHP applications were written in a
216.
▲
by
hakre
6y ago
Thanks for commenting, this one worked for me.
217.
▲
by
hakre
6y ago
Drag and drop file uploads always worked very well via FTP. Would be sad to see a degradation on something that was quite inter-operable and stable regardless of Javascript and its various Browser APIs.
218.
▲
by
hakre
6y ago
Thanks for your quick feedback. And how do you share the context / documentation which yaml file is intended to be called by which ansible utility with which utility parameters and switches? I ask b/c this is normally the problem
219.
▲
by
hakre
6y ago
Yes, that clarifies a lot. And yes, one repository per configuration (per customer code). Is it that you have one inventory per customer configuration? Or how do you manage multiple inventories in this setup?
220.
▲
by
hakre
6y ago
In the intended anyone, anywhere (specifically you wrote outside AWS) scenario you describe, is AWS offering professional support for Bottlerocket?
221.
▲
by
hakre
6y ago
Would you say that this can be compared to what leetrout commented with the difference that instead of scripts there is only a single command? Is the playbook always called "play.yml"? And how do you handle multiple repositories (
222.
▲
by
hakre
6y ago
How do you document how you call ansible within ansible if I may ask?
223.
▲
by
hakre
6y ago
Yes, that's why humans can read it on Github. Many people put even ASCII art into it (and restrain from actual HTML tags despite those are just fine in Markdown). So actually no disagreement from my side on that one, at least for me. Y
224.
▲
by
hakre
6y ago
Not so sure if it "must" be _one_ config file. I also don't think that the format matters more than it's use. Reminds me of some good advice in The Pragmatic Programmer, should be (simple) text-files for editing and (reg
225.
▲
by
hakre
6y ago
Good point, never had a problem to place the configuration files where they belong to, be it in the project root or not, until I figured it out. That's what software configuration management is for, and SCM is obviously in place (given
226.
▲
by
hakre
7y ago
but isn't it an antipattern to generate change-logs from commit subject lines?
227.
▲
by
hakre
7y ago
the 50 chars is for the subject. the commit message (body) has no character limit (apart from a character limit per line).
228.
▲
by
hakre
14y ago
As long as you registered the trademark this first of all is your legitimacy - that's why you register it. This registration has been opposed so I assume now PSF via their UK counsellor will add some evidence to the opposition. If the oppos
229.
▲
by
hakre
14y ago
The UK company didn't miss to exactly take the same international classes (009, 042) the PSF had choosen back in 2004 when they registered the PYTHON mark with the US copyright office. So that's more distinct than what others do, even if so
230.
▲
by
hakre
14y ago
Well, the question itself is stupid not because something is obvious in the outcome, but because obviously nobody can predict the future. And using simple words is not hostile, at least using the term "stupid" in my previous comment had no
231.
▲
by
hakre
14y ago
This is a stupid question to ask. Naturally they will not loose their right to use the name.