Marlon Falzetta
Matta,
The problem is that I need to be at the same directory level of the app (backend) to run the jhipster-ionic yo command.
What I was doing was creating a directory for the ionic app (mkdir security-app) and inside that directory (cd security) I execute the create command (jhipster-ionic yo).
The jhipster-ionic generator may be smarter to allow the creation of any directory (since I pass the path of the app backend) or at least warn that I must be at the same directory level.
You comment on this in the article, as below:
If you have your blog application at ~ / blog, you should run this command from your home directory (~).
But it does not stand out and it is not usual to have to execute a command inside a specific directory, mainly when the complete path of a target directory is informed.
Thank you for your help.
Greetings.
Matt Raible
Marion: can you please create an issue in the Ionic for JHipster project to make these instructions more prominent. Any ideas you have would be great.
Alireza Akbari
Thank you for the great work on ionic-jhipster and the article!
Matt Raible
You’re most welcome! I’m glad you like it. 
Er Balvinder Singh
Hey Matt, thanks for this awesome generator, today i was creating a new application. It asks me to go with ionic 4, when i say yes there is some error
? Try Ionic 4? Yes
[INFO] Existing git project found (/media/balvinder/Content/Git_Projects/SIMBALAB/latest/easygov-ui). Git operations are
disabled.
Preparing directory ./easygov - done!
[ERROR] Unable to find starter template for oktadeveloper/jhipster
If this is not a typo, please make sure it is a valid starter template within the starters repo:
https://github.com/ionic-te…
⠸ Looking up starter
events.js:183
throw er; // Unhandled ‘error’ event
^
TypeError: Cannot set property ‘author’ of undefined
at module.exports.install (/usr/lib/node_modules/generator-jhipster-ionic/generators/app/index.js:153:28)
at Object.<anonymous> (/usr/lib/node_modules/generator-jhipster-ionic/node_modules/generator-jhipster/node_modules/yeoman-generator/lib/index.js:418:27)
at /usr/lib/node_modules/generator-jhipster-ionic/node_modules/run-async/index.js:25:25
at new Promise (<anonymous>)
at /usr/lib/node_modules/generator-jhipster-ionic/node_modules/run-async/index.js:24:19
at self.env.runLoop.add.completed (/usr/lib/node_modules/generator-jhipster-ionic/node_modules/generator-jhipster/node_modules/yeoman-generator/lib/index.js:419:13)
at runCallback (timers.js:810:20)
at tryOnImmediate (timers.js:768:5)
at processImmediate [as _immediateCallback] (timers.js:745:5)
but it works fine with ionic 3
Matt Raible
I haven’t tried this module with Ionic 4. It sounds like it doesn’t work and we’ve got some work to do. Thanks for the heads up.
Er Balvinder Singh
Ohk i will be looking forward to the update
Matt Raible
It sounds like there’s some things I need to fix in the entity generator. Can you please add an issue on GitHub with the steps to reproduce? The easiest thing to do is likely to run jhipster info in your nms project. Then copy/paste the output into the issue. This should tell me all the JHipster choices you’ve made, as well as the structure of your entities.
Matt Raible
Not yet. I started implement it, but ran into issues and gave up. I’ll try to find time to re-examine in the next few weeks.
Matt Raible
No need to close the issue. I haven’t made time to look into it yet. FWIW, it shouldn’t matter what you call the app name.
Илья
Hi! Is there a way to manage push notifications from the jHipster’s server code?
Matt Raible
I’ve added Ionic 4 support on the master branch of Ionic for JHipster. To try it out, run the following commands:
git clone GitHub - oktadev/generator-jhipster-ionic: Ionic for JHipster 💥
cd generator-jhipster-ionic
npm link
Then create a new app and try it out!
yo jhipster-ionic
Mark Gargan
Consistently have found you’ve already written blogs about fast ways for java devs to get to production. Nice one!
Matt Raible
I’m sure there is, but I haven’t tried. I’d suggest doing some research and trying it yourself. If you run into issues, post your questions (and stack traces) to Stack Overflow and use the “jhipster” tag.