menu

Mockoon

Mockoon's official community. Get help, discuss new features.

Channels
Chat
view-forward
# All channels
view-forward
# General
view-forward
# Announcements
view-forward
# Bugs
view-forward
# Features
view-forward
# Help
view-forward
Team
Show previous messages

July 2, 2019 at 2:39am
Just curious if there is anyway to quickly save and export an environment?
  • reply
  • like
hi
  • reply
  • like
yes, top menu there are import / export options that allows you to save everything as a JSON
  • reply
  • like
if you want to export just the current environment or route you can, by right clicking on it, and clicking on "Copy to clipboard". Then just paste in a new file.
  • reply
  • like

July 3, 2019 at 12:26am
Any keyboard shortcuts for it?
  • reply
  • like
no not yet
  • reply
  • like
Oo okay. I'll see if I can hack something together then.
  • reply
  • like
there are keyboard shortcuts for other features, like deletion, duplication, etc but not for import / export. Feel free to open a ticket on the repository :)
  • reply
  • like

July 4, 2019 at 3:30am
Opened a ticket :)
  • reply
  • like
thank you :)
  • reply
  • like

July 8, 2019 at 2:52am
Anyone managing the repo o.O? The ticket have been opened for 5 days.
  • reply
  • like
I am nearly the only one maintaining Mockoon, and I have very little time these days to work on it. It's a side project, I have a family with 2 kids, and they are the priority, so your ticket will probably be open for some months before it gets done.
  • reply
  • like
In the meantime, if you want, you can submit a pull request with the changes, and it may accelerate the process a little bit.
  • reply
  • like

July 9, 2019 at 2:06am
Ahh i see. I will open a PR in a few days then. If you need any help, I would be glad to try to help.
  • reply
  • like
:)
  • reply
  • like

September 25, 2019 at 7:31am
Is there a Windows 32 bits version of Mockoon somewhere?
  • reply
  • like
Not yet, what do you need it for?
  • reply
  • like

October 28, 2019 at 2:43pm
I've updated Mockoon from 1.4.0 to 1.5.1 and suddenly all my routes and environments are gone. Is there a way to restore them?
  • reply
  • like
I've never encountered this. Best guess would be that data got corrupted during migration. But 1.5.0 and 1.5.1 migrations functions does not much and have been tested thoroughly. If data is not "secret" you can send them to me, and I can have a look and run in dev mode so I can debug. Otherwise, you can open you user data folder (c:/.../Users/xxx/AppData/Roaming on Windows, ~/.config on Linux and ~/Library/Application Support on macOS.) ./mockoon/storage/environments.json file and compare with a test file on the GitHub repository (https://github.com/mockoon/mockoon/blob/master/test/data/basic-data/environments.json) to see if the structure changed. If it's related to your data themselves maybe it's another problem.
Edited
  • reply
  • like

November 1, 2019 at 1:57pm
is there an option to update the auto save location
  • reply
  • like
its difficult to maint the data as I'm not getting option to save realtime data at specific location
  • reply
  • like
I've never encountered this. Best guess would be that data got corrupted during migration. But 1.5.0 and 1.5.1 migrations functions does not much and have been tested thoroughly. If data is not "secret" you can send them to me, and I can have a look and run in dev mode so I can debug. Otherwise, you can open you user data folder (c:/.../Users/xxx/AppData/Roaming on Windows, ~/.config on Linux and ~/Library/Application Support on macOS.) ./mockoon/storage/environments.json file and compare with a test file on the GitHub repository (https://github.com/mockoon/mockoon/blob/master/test/data/basic-data/environments.json) to see if the structure changed. If it's related to your data themselves maybe it's another problem.
I didn't have lots of data so I managed to restore it manually. Anyway thanks for the detailed information!
Edited
  • reply
  • like
ok, glad everything works again! Still, would have been curious to check where this bug came from.
  • reply
  • like
not yet, and I think it's not reached by an issue, so feel free to open one
  • reply
  • like
Show more messages