I have a question
Can I custom panel admin when app is already created?
In the documentation https://strapi.io/documentation/3.x.x/advanced/customize-admin.html#customization is written a project should be created in the dev mode with --dev flag, but I worked since 2 weeks on the project which I created without this flag, but now I want to add to admin panel one simple component and rebuild panel admin. Is this possible?
it's possible but the process is not easy.
What I would suggest is to create a dev app that has the same apis as your prod one. To do so you can follow step 1 and 2 from this issue.
Instead of recreating your apis just copy the api folder from your prod app into the dev one (if you made relations with the user model copy the ./plugins/users-permissions/models/User.settings.json file into the dev app, don't forget to restart your server).
Once you completed your modifications. Run npm run setup --plugins at the root of your dev application to make sure the build completes flawlessly.
At this point, you can reinstall Strapi globally npm install strapi#alpha -g.
Here you have two options, either copy your modifications into your prod application and run npm run setup --plugins at the root of the app or copy the generated build folder from the dev application into the other one.
Hope this helps.
Related
I used jetstream laravel authentication and I used npm run dev and keep it running on my cmd while I developed my project locally. Everything was OK till here. But now I want to upload on a shared hosting. And I got it that I need to run npm run build now. I have run it locally and uploaded the files but my ui of my project has been all scattered and misplaced. So I know I have missed a/some steps. What really have I missed out or have wrongly done.I am stuck now.
Regarding my web hosting ,I have my project files outside the public_html. All the public files are moved in this folder public_html.My database and my application working fine except the ui is messy.
I have find out a way but still do not know whether it is the best solution or proper one.
What actually the scenario is that the build folder of the npm run dev is folder project_folder/public/build but I have my project files outside the public_html folder. So it was unable to find the manifest.json in the folder project_folder/public/build. It was not working ,the UI is very ugly. Then, I put only the manifest.json in project_folder/public/build but the app.####.cs and app.###.js is kept in the public_html/build/assets. And now it is working fine. Hope this help someone like me, even though it might not be the right approach.
So, I installed everything as directed in the documentation, both the node-template and front-end template. Then, I went on to run ./target/release/node-template --dev --tmp in the node-template directory, which worked fine and was able to produce blocks. After opening a new terminal and moving to the front-end template, I used the command yarn start. This didn't produce any error and I was redirected to https://localhost:8000/front-end-template. The site took too much time to load and I was not able to see the Polkadot UI. Looks like the front end could not be integrated with the node-template.
Any help would be much appreciated.
In the front-end template directory while the node-template is running,
run yarn install and after everything works well then yarn start
OR, remove the front-end template and clone a new one if you didn't make significant changes to old one.
OR, stop the node-template and run this command ./target/release/node-template purge-chain then start the front-end.
I used do these and get this problem fixed, quickly!
Using the docker compose playbook here, I cannot figure how to then use the admin panel to install an extension.
We have the auth.json file present in our user's ~/.compose/auth.json file, and is mounted in the proper container as suggested by the README. However it's not clear how to run the setup container with the M2SETUP_USE_ARCHIVE env variable set to false. Doing so fails always.
So far, the only thing we got to work is a Magento 2.1 instance, but the Admin panel seems to be missing functionality (The Components Manager is missing from the System tab for example).
How to get that setup to work properly? What's the best way to have a clean Magento instance with extension support to play with?
I have deployed a node.js app in Bluemix using cf push. I have removed the start: entry from manifest.yml. In Bluemix I have set the environment variable BLUEMIX_APP_MGMT_ENABLEto devconsole+shell+inspector. This restages the app.
But when I open the App Manager by adding /bluemix-debug/manage/ I get a 404 error.
When I start Live Edit on the same project from DevOps Services I can open the App Manager. But I don't see what is different, it also seems to set the environment variable only.
What am I missing?
The Live Edit tool will automatically add 256MB to your application to facilitate execution of the additional features, which is likely why it is working with Live Edit.
Manually enabling the feature, however, will not automatically bump up the memory. Can you try adding some more memory to your application and restaging?
There are a couple of other limitations; refer to the Restrictions section on the App Management docs.
EDIT: Found issue in comments below. If command: node app.js is in manifest.yml, or if you are using -c with the CF CLI, it overrides the buildpack's ability to start the development utilities in App Mgmt. This happens even if you have the start command correctly specified in package.json or Procfile. To fix this, remove the manifest.yml entry, delete the application, and restage the application.
Although I'm new to Laravel 4, there has been one question on my mind since day one which I cannot seem to understand, nor find any information on.
My plan is to build an open source web application, which other users will be able to download and use on their own server. Now my current way of working is:
Install Laravel with composer
Add packages to composer than I need for the application
Start coding: editing files directly inside of app/ (global.php, routes, controllers, views, migrations etc).
Keep all of my assets within /public/assets/
This works fine for me, and I have no problems with it. However the question is:
How will I deploy the application to users if I build it this way? If they install Laravel via composer, all of the files within /app will be default (obviously), so how would I go about getting my edited + custom files into their install of Laravel?
Do I have to build the whole application as part of my own bundle? Or is there some kind of way composer can pacakge what I've done to solve this problem I can see happening?
I'm just throwing words out, if someone could explain and point me in the right direction that would be great.
Thanks.
You can just chuck all your files on github. You dont need to include composer. People can download composer and run it from the install directory (or if they have it globally run it from there)
If you run a composer install with laravel 4 only, it will download all fresh. In your case you just have all the library's in place already. So for future updates you as a developer can easilly upgrade to a newer version. The "users" can simply say "git pull" to update their instance. You still need composer to do your initial install (db seed, post install steps etc)
At least that is my point of view. Just look at a simple laravel 4 bootstrap example https://github.com/andrew13/Laravel-4-Bootstrap-Starter-Site it also holds all the files.