Where does the standalone Postman client for Windows save collections when working offline?
To clarify, I want to find where Postman saves collection files to by default when online syncing is disabled. I am not trying to export my collection as a JSON file.
I've looked in %LocalAppData%, My Documents, and Program Files, but I don't see where Postman saves its collection data.
It looks like Postman uses LevelDB. On Windows, I found my Postman DB located at:
%HOMEPATH%\AppData\Roaming\Postman\IndexedDB\
ps: %HOMEPATH% is path for C:\Users\xxxx\
also worth mentioning: %APPDATA% is a shortcut for C:\Users\xxxx\AppData\Roaming\
According to Piere F, macOS users can find it under:
~/Library/Application Support/Postman/IndexedDB
ps: Note ~ is path for /Users/userAccount/
According to David, Ubuntu users can find it under:
~/.config/Postman/IndexedDB
Postman is using Chromium offline storage capabilities because at the end it's a SPA running inside Chromium (Electron technology).
From Postman's top menubar:
Select View → Show Dev Tools
Select the Application tab
In the sidebar, open Storage → IndexedDB → postman - file:// → collection_requests
In windows, postman v9.6.2 I was able to restore collections by pasting the IndexedDB folder in the following path:
\AppData\Roaming\Postman\Partitions\<GUID>\
On Mac: The json files were automatically backed up (/Users//Library/Application Support/Postman/backup-YYYY-MM-DDTHH:mm:ss.SSSZ.json) but it is not documented anywhere.
You just have to reimport them
This support documentation helped me recover my collections after the postman application stopped working.
https://support.postman.com/hc/en-us/articles/360035071313-How-to-recover-my-data-
If you weren't logged in to the app and using it offline or in the
Scratch Pad mode then your data won't get synced to our servers and
stays local to your instance. In this case, try following the steps
below:
Look for the backup files under the following folder:
%appdata%\Postman\for Windows ~/Library/Application
Support/Postmanfor macOS ~/.config/Postman for Linux
Backup file names will be similar to
backup-2020-02-26T23-13-43.082Z.json (date or time will be different
for you).
Alternatively, if you just want to look at the collection, you can export it into json format from the collection menu.
We work offline. So for Postman Scratchpad (official offline usage):
On Windows: %HOMEPATH%\AppData\Roaming\Postman\Partitions\
On Mac: ~/Library/Application Support/Postman/Partitions/
Simply backup or share the entire directory when you want to synch.
For the version Postman from Google Chrome extension, you need copy all files from path:
"%LOCALAPPDATA%\Google\Chrome\User Data\Default\Storage\ext\fhbjgbiflinjbdggehcddcbncdddomop\def\IndexedDB\chrome-extension_..."
The files inside path above contains all history and collections from Postman
Linux Chrome or Chromium Postman extension storage path Location
/home/{USER}/.config/chromium/Default/Storage/ext/fhbjgbiflinjbdggehcddcbncdddomop/
Thanks.
If you are using a snapped Postman on Linux, let me save you some time.
Copy all the content from your source snapped Postman UNDER (as the target GUID can be different)
/home/username/snap/postman/<id>/.config/Postman/Partitions/<standalone GUID>
to your target snapped Postman UNDER
/home/username/snap/postman/<a different id>/.config/Postman/Partitions/<a different standalone GUID>
Make sure you respect the target postman id and partition GUID.
Win10:
You have to back up your old Postman
C:\Users%user%\AppData\Roaming\Postman\IndexedDB
Then copy it to the same location of the new Postman installation.
This will recover all your collections.
In Debian-like systems, using Postman v7, I found a backup of all the collections and environments saved as JSON in ~/.config/Postman with the prefix backup-.
eg: ~/.config/Postman/backup-timestamp.json
Also, found a recent support article in Postman documentation:
How to recover my data
Windows 10, I copy these folder to another and worked.
C:\Users<username>\AppData\Local\Google\Chrome\User Data\Default\IndexedDB\chrome-extension_coohjcphdfgbiolnekdpbcijmhambjff_0.indexeddb.leveldb
I need some help to determine why my VSTS build agent doesn't create an artifact in the drop folder
I have a solution that contains a website project (not a web application) and a logic project that i'm trying to build the website via VSTS. The build complete's correctly when i reference the solution as part of the "Process" step but nothing is added to the drop folder for the release process.
I have modified my build arguments to look for a publish profile that has been saved to the app_data/PublishProfiles (called vstsbuild) on the website project. The website doesn't have a project file but it does have a website.publishproj file at the root of the website.
Any idea why it won't publish an artifact would be helpful
VSTS Publish Logs
our PWA lives here: https://m.quemesa.com and we also have native apps with the same codebase.
However, we are not targeting the Cordova Browser platform (because it does not seem to be officially supported and I can’t see what benefit it adds) so we have to add slightly different code for our PWA compared to our native app builds. For example, In the PWA, we use the pure Google Analytics solution which requires 2 lines of javascript in the index.html.
For our native builds, we use the Cordova GA plugin, so this is not required. In the PWA we don’t need to link to Cordova.js and Vendor.js for exmaple (they get a 404 error). In the native apps we do.
Currently I am manually editing (yuck) the output folder before uploading to Azure for the PWA.
Is there some way to edit the Ionic Build Process so that I can either have 2 versions of the Index and it grabs the one it wants for the output folder depending on the build type OR it can modify the html file at build time?
The current ionic build tool alone doesn't support this.
You could just have 2 versions of index.html and a small script to swap between them and build both versions.
It's also something you could do with a "full" CI build tool. Since you mentioned Azure you could make use of Visual Studio Team Services. There are existing tasks available for npm (to install ionic, run a PWA build) and running command/PowerShell scripts. It may be easier to start off by setting up an "agent" VM with everything it needs to build your app (node, ionic, Android studio, etc) then build your build process up from there.
I use gulp-preprocessto update index.html on build depending on platform targeted. The idea of the preprocess is to generate a target index.html before the ionic serve/build with the exact declarations required for the mode selected, pwa or native. More details on this post "Using Ionic/Cordova app sources as PWA"
How I can check for WFFM version that have installed in Sitecore 8.
I was checking in List of Package inside Data/Packages folder . Is this correct way to do this ?
That's one of the options, but it's not necessarily correct. One can upload a package to that folder but never install it.
You can also check WFFFM dlls in the bin folder and see their version.
And maybe the most reliable way: login to Sitecore Desktop, change database to core and in Content Editor find /sitecore/system/packages/installation history node. There should be a list of all packages which are installed in your Sitecore application including their versions.
Look in the sitecore general log at application startup, all dlls are listed including version numbers.
I found one more way All Application ==> System ==> License detail ,there i found the version of WFFM.
I have findout ChilkatDotNet2.dll library is located in sitecore bin folder and can't be load in case if enabled 32-bit app support in app pool.
I removed this library and it seem like web site is working fine.
Is it necessary for Sitecore to have it?
The library might have been installed on your Sitecore instance with a module (I believe the Email Campaign Manager uses it). If that's the case, the module installation files probably contain both a 32-bit and a 64-bit version and it would be up to you to use the correct one for your system.
That library is not part of the libraries that ship with Sitecore.
So removing it won't have any effect on Sitecore, but may have on custom parts of your application.