I'm using CouchDB 1.5 on Ubuntu Desktop 14.04. I'm having trouble understanding how the Fauxton app got installed (as I don't recall installing it.)
I found the UI at [myhostip]:5984/_utils/fauxton/ but I can't locate all of the files on disk. So the questions are:
1) I'm thinking the Ubuntu Software Center installed some sort of package, but wondered if someone could confirm that?
2) Where the application files on disk?
Fauxton is a part of couchdb, in fact it is the default user interface for 2.0. Most likely your fauxton is in
/usr/local/share/couchdb/www/fauxton
to find out for sure open your your config file
http://localhost:5984/_utils/config.html
and look for
__utils in httpd_global_handlers section and it will tell you where couchdb utilities are installed. In the utilities directory you should see a fauxton folder which contains the fuaxton files.
Don't worry though no third party installed it. It is a part of couchdb package. Here is the repo on github.
Went further based on guidance from #Akshat; it turns out that the Fauxton application code was on disk in /usr/share/couchdb/www/fauxton/js in a file named require.js. All code and templates were there, minified and munged.
Related
I'm currently working on a github project mainly focused on windows users, written in Java. Install4j allows for easy .deb/.rpm etc. package conversion...
We could just ditribute the .deb on the download side, but when looking at gitlab a while ago, I saw, that Gitlab is using packagecloud.io as a hosting service for their packages (usingtheir own domain), so they can be updated using apt-get.
My question is, if there is a free service working just like packagecloud.io (not launchpad or similar with baazar and that advanced stuff) which can either be hosted on our own server or a public server. Or if there even is a downloadable version of packagecloud.io which we could use on our own server.
You can configure Travis CI to run extra commands when the build succeeds. You can put in some conditions, so that the deploy stage will only be run if commit happens to have a tag name. See the deployment documentation to get going.
A number of providers are officially supported, among which PackageCloud.io.
You might find the dpl utility useful, as it assists with writing and testing deployment settings.
Check out OpenRepo: https://github.com/openkilt/openrepo
I think this is what you're asking for. This is a package hosting server that can make packages available for both Debian (APT) and Red Hat (RPM) files.
I'm trying to profile a web application with xDebug and Webgrind since I'm doing it in a remote Linux server. For some weird reason it doesn't show call names or file source. I was suspecting that there might be some kind problem with readying the script files (not sure if it's doing it) but giving target folders 777 didn't make any difference. Does anybody have a clue where I'm failing?
Thanx!
The webgrind version found on google code does not work for xDebug 2.3.
Here is a fork that works: webgrind
Ok, 24h later:
Seems that webcache grind doesn't support cachegrind file function compression feature that was introduced in xDebug 2.3 (released 2015). The latest webgrind was released ~2008-2009 so makes sens that it doesn't work. The same applies to WinCacheGrind client. Currently seems that only Windows cachegrind analyzer is qCacheGrind and linux client kCacheGrind
When I maange to find some free time I'll fork the project and make it compatible with compression.
I have node.js installed on my mac. However I am not able to find the the source code.
The 'node' binary file is located /usr/local/bin however since its binary, I can not view it.
For example I want to see internal of console.log function.
On joyent github I can see the code but I want see it when I am offline via some editor like webstorm.
https://github.com/joyent/node/tree/master/lib
Can someone please help.
Thanks
Locally you have Node.js installed. To make your life easier, Node.js developers have already compiled Source into runnable Application.
Because you downloaded already compiled Node.js (that is OK, and sensible), you need to also download source-code if you want to access it offline.
Downloading source-code is just as easy, you can grab the latest code available at the same location as you specified: https://github.com/joyent/node. Look for "Download ZIP" button on the bottom right.
In case of webstorm this link will help - http://www.jetbrains.com/webstorm/webhelp/node-js.html - see "Configuring Node core module sources"
What is the recommended way to deploy Node.js on Ubuntu 12.04 in a production environment?
I saw this ppa but I don't know if is well maintained or if it will and if is a source in witch one can trust.
I know that is easy install Node.js manually, but seem to me that install it using the Ubuntu packages manager will allow me safe some management time and will be more integrated with the way the underlying server is being currently management. So, what are your recommendations? Thanks in advanced.
we are using Chef with the existing node.js cookbook
Well, after read lot of posts and pages that talk about Node.js deployment-installation, I must said that Chris PPA is mentioned in tons of them as an official source. Beside one can see her PPA linked at the Github Node.js wiki.
So, seem to me that is trust enough to be used in production, what made it the choice if you want keep your system updated using standards Ubuntu tools.
I am looking for a good way to install an application I developed with all its dependencies in a fancy way. Currently I have a big make file that downloads, unpacks, compiles and installs all dependencies. This however is a little tedious, since there are quite a few dependencies and the make file is getting larger and larger which eventually will be hard to maintain. Therefore I am looking for a packaging tool with the following features:
It should be a light weight package manager which is very easy to install (or even installs itself and afterwards all my dependencies)
The destination of the installed binaries, libraries etc. should be customizable
Each installation process of a dependency should be easy configurable
It should be possible to include self written scripts that get executed at a specific point during the installation process (in order to manipulate make files, flags etc)
No admin rights should be necessary since all clients that install my application will not have admin rights and are not able to use an already installed package manager
I do not know if this kind of software exists. I myself don't have much of experience with packaging tools.
Thx in advance for any link, hint, suggestion!
opkg is something thats based on ipkg (now defunct) and originally dpkg. Its used in embedded systems. Light weight for sure.
ports from crux linux (www.crux.nu)?
A quick search returns InstallJammer. I would propose make debs and rpms and tarballs and stick with standard installation process (root privileges and such)m but if you can't do that, then, well, you can't.
I'm sure you know how suspicious it would look for the user.