Timeline for Version control of a website : dev/production front-end files
Current License: CC BY-SA 3.0
16 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 18, 2015 at 20:38 | audit | First posts | |||
| Sep 18, 2015 at 20:39 | |||||
| Sep 10, 2015 at 13:43 | history | edited | Doc Brown | CC BY-SA 3.0 |
added 34 characters in body
|
| Sep 10, 2015 at 13:42 | comment | added | Doc Brown | ... Note that the origins of the term artifact (not specificially for software development) come from the latin words artis ("craft") and facere ("to make"). In this more general context, it stands for human and/or technically produced things. | |
| Sep 10, 2015 at 13:30 | comment | added | Doc Brown | @Daenyth: the Wikipedia article is far from beeing perfect, nethertheless it says exactly what I wrote above - in some contexts (like black box testing, where the executable is the input file of the process) the term is used differently. And I already edited my answer to make clearer which meaning of the term I am referring to. | |
| Sep 10, 2015 at 12:30 | comment | added | Daenyth | @DocBrown Your link seems to support that it refers to the output - "Build tools often refer to source code compiled for testing as an artifact" | |
| Sep 10, 2015 at 7:45 | vote | accept | Antonin Cezard | ||
| Sep 10, 2015 at 5:45 | comment | added | Doc Brown | @BasileStarynkevitch: see my edit. | |
| Sep 10, 2015 at 5:44 | history | edited | Doc Brown | CC BY-SA 3.0 |
added 232 characters in body
|
| Sep 10, 2015 at 5:38 | comment | added | Doc Brown | @Daenyth: AFAIK the word artifact means primarily manually produced parts in software development. You are correct that in some contexts people speak of "build artifacts", because what the compiler produces is indirectly a result of the manual programming action. | |
| Sep 9, 2015 at 20:21 | comment | added | Basile Starynkevitch |
It is not exactly always true: for bootstrapped compilers, you may need to put generated files under VCS. A typical example is Ocaml's bytecode boot/ocamlc or GCC MELT melt/generated/*.cc files
|
|
| Sep 9, 2015 at 18:49 | comment | added | Daenyth | Your wording is confusing. "Artifacts" frequently refers to the output of compilers or generators, not the input. | |
| Sep 9, 2015 at 17:01 | history | edited | Doc Brown | CC BY-SA 3.0 |
added 297 characters in body
|
| Sep 9, 2015 at 16:53 | comment | added | Doc Brown | @topleft: From the "production server"? Not necessarily, the source code is in the repo, you can build it from everywhere where you have access to source control and to the production server's file system. So whereever you prefer, from a dev machine, from a decicated build machine, or maybe directly on the prod machine. But see also my added paragraph after you wrote your comment. | |
| Sep 9, 2015 at 16:48 | history | edited | Doc Brown | CC BY-SA 3.0 |
added 812 characters in body
|
| Sep 9, 2015 at 16:43 | comment | added | Antonin Cezard | does that mean when the site goes to production, it's needed to build it from the production server ? or maybe just host the build (which is not versionned then) | |
| Sep 9, 2015 at 16:36 | history | answered | Doc Brown | CC BY-SA 3.0 |