Convert ENV to MSGPACK
Turn ENV files into MessagePack. The same structure and key order in MessagePack, with integers, floats, booleans, null, text, lists and maps keeping their types and dates as text.
Converted in an isolated sandbox on our serversDeleted after 24 hours
Drop ENV files on the dialor turn it to pick what to do
Dotenv settings as compact MessagePack.Your KEY=value lines become one MessagePack file with the same structure and order.
What you get
One MessagePack file with the same structure and key order as the ENV file. Integers, floats, booleans, null, text, lists and maps keep their types in the output.
MessagePack is binary JSON: the same values as JSON in a compact byte encoding. The file is not readable as plain text.
What changes
Dates are kept as text, not as a date type. If a program reads the MessagePack file, it receives the date as a string.
Going the other way
To turn a MessagePack file back into KEY=value lines, use MSGPACK to ENV.
ENV and MSGPACK.What each format is.
The formats
Dotenv
KEY=value lines that hold environment variables for an app.
- Extensions
- .env
- MIME type
- text
/x -env - Kind
- Text and data
MessagePack
Binary JSON: the same values as JSON in a compact byte encoding.
- Extensions
- .msgpack .mpk
- MIME type
- application
/msgpack - Kind
- Text and data
In your code.The same ENV to MSGPACK conversion through the API, for your app or your agent.
$ cv convert report.env report.msgpack$ cv convert report.env report.msgpackQuestions.What people ask about ENV to MSGPACK.
Yes. The keys come out in the same order as in the ENV file.
Yes. Integers and floats keep their types, and so do booleans and null.
They are written as text. MessagePack holds them as strings, not as dates.
Yes. MSGPACK to ENV converts it back to KEY=value lines.