| import NonFungibleToken from 0xNONFUNGIBLETOKEN | |
| pub contract TenantService: NonFungibleToken { | |
| // basic data about the tenant | |
| pub let version: UInt32 | |
| pub let name: String | |
| pub let description: String | |
| pub var closed: Bool |
.env file for me sparing me the need to pollute my session with environment variables.
I've been using Fish shell for years which is great and all, but one thing that has got me frustrated is using it with .env files.
When attempting to run source .env in a project, I usually encounter this problem:
This is a collection of the things I believe about software development. I have worked for years building backend and data processing systems, so read the below within that context.
Agree? Disagree? Feel free to let me know at @JanStette.
Keep it simple, stupid. You ain't gonna need it.
| /* | |
| Demo program illustrating usage of gomplate as a library. | |
| This program will accept an input file and run it through the templating | |
| engine as both the values dictionary as well as the template file. It will | |
| repeat the process until the templating result stops changing, and print | |
| the result to STDOUT. | |
| This program add the gomplate datasources and functions to the golang | |
| text/template engine. This requires the input to be have the gomplate |
oc get pod -o jsonpath='{range .items[*]}{"SPEC: \n LIMITS : "}{.spec.containers[*].resources.limits}{"\n REQUESTS: "}{.spec.containers[*].resources.requests}{"\n"}{end}'
oc get pod -o jsonpath='{range .items[*]}{"NAME: "}{.metadata.name}{"\nSPEC: \n LIMITS : "}{.spec.containers[*].resources.limits}{"\n REQUESTS: "}{.spec.containers[*].resources.requests}{"\n\n"}{end}'
| package api.resource; | |
| import javax.ws.rs.*; | |
| import net.hamnaberg.json.*; | |
| @Path("/events") | |
| @Produces("application/vnd.collection+json") | |
| @Consumes("application/vnd.collection+json") | |
| public class EventResource{ |