From the user POV, putting.

Filipovich: And upload in the size you want actually displayed.

Pouch: If you look inside the existing configs you should be able to use one to setup a seperate directory for wordpress install

Filipovich: Upload in the size you want displayed

Antrobus: Remeber to restart apache after making those changes

Dehart: Can: Google result for gnu image GIMP –

Campeau: Hi guys. what’s the best way to set a variable inside wordpress that I will then use in functions.php? for instance, an api key

Joynt: Use an ENV variable instead

Hannafin: Zagaza are you using apache ?

Filbert: Dont know if it will use apache or ngxinx in the end, why?

Filipovich: Zagaza: store it in wp_options

Guella: Zagaza because you can set an env variable in the hosting config

Berlove: Zagaza for apache, it would look like this

Filipovich: Nak: that’s a terrible idea

Medas: SetEnv MY_API_KEY “ABANSN092N51029N510N”

Carthon: Zagaza for nginx, inside your location ~.php$ { . } block, you would use

Rieff: Fastcgi_param MY_API_KEY ABANSN092N51029N510N;

Filipovich: Nak zagaza if it’s for WP, the solution should be wp-centric. Store it in wp_options like any other API key would be stored.

Bahrke: How is that a counter point to what i’m saying ?

Barriga: You’re saying “store it like any other API key would be stored”

Daughety: Well i certainly would never store an API key in a database

Machel: Nak what if the client would have to change it?

Filipovich: Yup. just like various “pro” plugins do, or like Yoast stores my Google UA key

Filipovich: I’d create a plugin to support that API, even if all it does is just store an API key in wp_options

Lapinski: Zagaza sure set it up in the database

Hanusey: It’s just wordpress, who cares ?

Bolay: Don’t even bother using version control while you’re at it

Butkus: Filipovich hmm where does those options end up in the admin ui?

Maccarini: Just zip it up and FTP it over

Molinini: If the client changes some of the code, who cares

Krom: Nak, what does version control have to do with anything now?

Filipovich: Zagaza: that’s up to you. You can create a plugin and plop something on the dashboard or in the customizer

Torbett: Zagaza what does a database have to do with environment configuration ?

Filipovich: Nak: it seems you have no idea what you’re talking about

Pomales: Because i disagree that you should configure environment in a database ?

Turocy: Ok so let’s run the scenario we’d like to snapshot the production data and pull it into a development/staging environment

Filipovich: Should every API key be stored in the server config? Google ****ytics, Formidable Pro license key, reCaptca keys, etc?

Miu: Filipovich what are you going to do now that all of your production environment data is in the db ?

Filipovich: Nak: no, I have no desire to pursue this with you.

Kremmel: Yeah because *you* don’t know what you’re talking about

Falasco: Nak: The p***ive agressiveness isnt’ needed.

Filipovich: OK. *USERS* need to be able to modify things.

Kettelle: Just because wordpress plugins are all doing the same stupid **** doesn’t mean they’re not noob

Sweed: Nak: Please help us keep Orchard a family friendly room, and avoid using foul language.

Hochschild: Databases are for persistent state

Mosure: API KEYs aren’t “state”

Filipovich: From the user POV, putting stuff in the Apache environment means that 1 it’s “hard coded”, 2 is non-portable i.e., moving WP to a new site, 3 obscured