I created a new Meteor project in WebStorm and it generated hello.html file which is the default page of the app, and hello.js file.
Now the thing is that I don't want these files to be named "Hello". How can I change the default/initial files of Meteor?
I searched references for these files in the project but I didn't find anyone, meaning that they are not defined hard coded.
Any help will be profoundly appreciated!
Edit: I just found out that I can name the initial file when I create a new Meteor project in WebStorm. I'd rather change it in the current project than creating a new one though. Is this possible?
if you create new project in command line then running meteor create appName will generate files appName.js, appName.html and appName.css
in general, it does not matter what are the file names in meteor. Naming starts to matter a bit more once you start organising files into folders, but for a start you can ignore that.
Related
I have two projects. The first project is a web-server that runs scripts. The second project exposes a collection of scripts that the first project runs.
I launch the web-server via a .vscode/launch.json entry.
I reference the program as ${workspaceFolder:first}/src/webserver.ts and reference the compiled js as outFiles: [ "{workspaceFolder:first}/**/*.js" ].
The webserver gets the request and launches the js file in the second project directory but doesn't use the source that's referenced by the source map.
If I try to add multiple outFiles the program tries to run the webserver.ts file instead of the .js equivalent.
Can anyone shed some light on the process of how the vscode debugger handles finding source maps or knows of a solution to getting the source from the .js in a different project directory to get recognized by the debugger.
Any help would be greatly appreciated!
I'm quite new at Node and Git, I've been working on this repository for a couple of days and I'm not sure how to make it work. It tells me to configure some vars but I don't quite understand how to. Which file should have the actual LOGIN, PASSWORD, SLACK, etc.(Or should I just type them in the terminal)? What should I be typing in the Node Terminal?
Neither am I sure how to run the github files since every time I call it in the terminal it types "No local config found" or "Cannot find module"
I have no clue how to go on, so any help would be REALLY appreciated.
https://github.com/nicolsc/slack-sigfox-last-message
Create a file config.local.js and store the parameters inside. each existing parameter will override the defaults.
the files named config.*.local are also added to .gitignore which self-explain that those kind of files are configuration files.
So I am trying to connect up my Jasmine unit tests in a VS2015 web project with the resharper test runner and thought I would use the Auto-generate _references.js file to save me having to type the references in each test spec. The Auto-synced _references.js file doesn't however include any javascript dependencies from the wwwroot/lib folder. Bower is definitely copying them to that folder correctly, but the synchronization is ignoring that directory. I thought the references generation might scan the web project looking for .js files to reference but it seems to have missed a swathe of them.
According to Mads Kristensen:
Whenever a .js file is added, renamed, moved or deleted, the _references.js file is automatically updated to reflect the changes.
This doesn't seem to be happening with .js files in wwwroot/lib. Is this on purpose? Do I have to turn auto-sync off and do it manually?
I have developped a Jhipster project.
I need to create a new one which will be quite the same (but not the same). I would like to duplicate the first project.
The second project would just have a different name and different main package name.
Is there a way to do that properly?
Thanks
Duplicate your project folder, in new folder edit .yo-rc.json file and change name and package. You may also want to change the rememberMeKey
Delete src folder
Run jhipster --with-entities to re-generate app with new settings
Copy back from old project what you've added
Delete yo-rc.json .... and generate your new entity then every thing will be ok (Tested)
I'm start to develop modules for DotNetNuke. I followed different tutorials(most by Chris Hammond) but there is something i don't like, and I'm searching a different way to do so.
He recommends to put a DotNetNuke installation, with IIS and SQL Server, on the developer PC and put your Project into the DesktopModules folder. I don't like it because i want to separate my project from DotNetNuke.
Is there a way to split the build/publish to different location like dll into folder x and all other stuff into folder y?
You could, but I don't really see the point. I see where you're coming from because it seemed awkward to me at first as well, but it really is the most efficient way to develop on the DNN platform. I have mine set up so all of my modules are in the same solution and branched in source from the root DNN folder. We don't keep the DNN core in source so the developer is responsible for that, although that may change at some point to keep versioning consistent.
By keeping your project located where it's installed, you can develop your modules the same way you'd develop any other web app you're building. If you make a change in markup you just have to save the file and refresh your page. If you change something in code just build and refresh.
If you really must keep them separate, you can absolutely do so (really the only benefit of this that I can see is that if you uninstall a module and accidentally click the checkbox to delete files - it happens - you don't have to worry about it). Create your project where you want it, change the Output Path to your DNN bin folder, and create post-build events to copy all of your .js, .ascx, and .css files (plus any others you may need - images, HTML files, XML files, etc.) to appropriate folder(s) in the DesktopModules folder. Just remember that you have to build the project every time you make ANY changes to test them, and you have to write/change your post-build events every time you add a new type of resource, change/add a directory, etc.
Either that or you can build an install package and uninstall/reinstall the module every time you change some padding in your stylesheet ... but I'd stick with keeping the project in the DesktopModules folder.
Sure you can do that.
Set up your solution and module projects anywhere, build the projects and copy the appropriate parts (such as the *.ascx , *.ascx.resx, *.dnn files) back to your website folder -
website/ DesktopModules/Your_module_name
Copy the module dll to the website's bin and you good to go.