Shulou(Shulou.com)06/02 Report--

This article introduces the relevant knowledge of "how to install and use cloudwall on tinycolinux". In the operation of actual cases, many people will encounter such a dilemma, so let the editor lead you to learn how to deal with these situations. I hope you can read it carefully and be able to achieve something!

In "cloudwall: an appstack that unifies nativeapp and webapp", cloudwall is a management layer built on counchdb+counchdbapp that can be directly used as personal cloud hosting documents and support cloudwall plugin development, but its wonderful utility is that it can be used as an webos to provide the utility of webappstack, similar to the engitor that we have been pursuing: the level between os and app, encapsulating the level of domainapp development stack and development tools. However, it is more powerful: it provides local, remote and consistent webapp development and distribution (in the form of seamless streamed to bs and anyinstance + inapp editor).

In fact, all these are basically the effects of counchdb, which integrates HTTP, which is a DB with storage, closely integrated with browser and JS, and supports hosting couchdbapp, document or APP. This APP is only composed of HTMLCSSJS. This mechanism provides at least three stacks for remote web, which meets the basic conditions for building APP: 1. Its http part eliminates protocol development, and web pages are easy to streamable. 2. Its DB property eliminates the need for storage logic development. It stream to local and each counchdb instance (replicate) the result is the same, to ensure that the data between the browser and the server can be local and remote continuous connection (in-browser os), local and remote, the most difficult to cross is this seamless stream. 3, the counchdb it uses uses the full-stack language JS, and each cloudwall app hosted in it is both a server-side program and a client-side program (nobackend webapp). However, just like tiddywiki: in fact, JS on the server side is only static document stream to client execution, and the server side only treats everything as a document but a synchronizer. Things like tiddywiki lack database hosting.

It can be said that it is the perfect combination of JS and couchdb that makes cloudwall, a lang and a hostingtime,runtime on the B side. In this sense, the "WEBAPP", whether local or remote, is through one end of the database stream. This is what the title of the article says: uniform native web appstack.

Next, we will explain how to build cloudwall on tinycolinux and explain all aspects that can be used as personalcloud in the process of using it.

In previous articles, we proposed a cross-local / remote DISKBIOS XAAS system and perfected a / system rootfs, which, as mentioned earlier, is a rootfs system with separate system and user libary, with only three folders / boot,/system,/usr and / local,/tce,/opt,/home,/vz corresponding to those mountable folders of tinycolinux under / usr. So from the beginning of this article, we will call the new tinycolinux dbcolinux, and the future release articles will be moved to it for practice, the following cloudwall is an example. In "cloudwall: an appstack that unifies nativeapp and webapp", cloudwall is a management layer built on counchdb+counchdbapp that can be directly used as personal cloud hosting documents and support cloudwall plugin development, but its wonderful utility is that it can be used as an webos to provide the utility of webappstack, similar to the engitor that we have been pursuing: the level between os and app, encapsulating the level of domainapp development stack and development tools. However, it is more powerful: it provides local, remote and consistent webapp development and distribution (in the form of seamless streamed to bs and anyinstance + inapp editor)-all of which we have been pursuing since bcxszy. Why is cloudwall so powerful? In fact, all of this is not difficult to understand, because excluding cloduwall, it is basically the effect of counchdb, which obviously integrates HTTP, itself is a DB with storage, is closely integrated with browser and JS, and supports hosting couchdbapp, document, that is, APP. This APP is only composed of HTMLCSSJS. This mechanism provides at least three stacks for remote web, which meets the basic conditions for building APP: 1, its http part eliminates protocol development, and web pages are easy to streamable. 2. Its DB property eliminates the need for storage logic development. The result of stream to local and every counchdb instance (replicate) is the same, ensuring that the data between browser and server can be connected locally and remotely (in-browser os), local and remote, the most difficult thing to cross is this seamless stream (since WEBOS can be compared to a cloud storage based with nativedev likehood appstacks, it must have a DB layer, so why not use DB's replicate to synchronize the network disk directly with app sync? In fact, the original W3C WEB standard was also prepared to prepare an error-free web storage,web sql,webgl,etc.. for WEB on the BS side. To provide nativedev-like appstack effects, but many practices are gradually abandoned. 3, the counchdb it uses uses the full-stack language JS, and each cloudwall app hosted in it is both a server-side program and a client-side program (nobackend webapp). However, just like tiddywiki: in fact, JS on the server side is only a static document stream to the client, and the server only regards everything as a document synchronizer (the server does not save the program logic only the data is very much like the micro end. In the micro-end's view, the standard facility that works best with B-end browsers is DB rather than logicserver.) . Things like tiddywiki lack database hosting. It can be said that it is the perfect combination of JS and couchdb that makes cloudwall, a lang and a hostingtime,runtime on the B side. In this sense, the "WEBAPP", whether local or remote, is through an end of the database stream (while couchdb also supports the traditional serverside applogic vs synced applogic). This is what the title of the article says: uniform native web appstack. Next, let's talk about building cloudwall on dbcolinux. I'm using gcc443 32bit, and I'm using otp_src_20.3.tar.gz (erlang). Js185-1.0.0.tar.gz is not only 2.1.1.tar.gz, but also 3.x zip-unzip.tcz,icu.tcz,icu-dev.tcz. All right, here we go.

Compile erlang,mozjs

Since the rootfs of dbcolinux is still in its infancy, some programs still need the original / directory layout to compile and run, for example, the / usr/lib referenced in the make meunconfig instruction must exist, otherwise, even if ncurses.tcz and ncurses-dev.tcz are installed, undefined reference will be prompted all the time, so here, in order to successfully complete the following compilation, let's restore it for a while. These empty directories are only expedient at compile time, and dbcolinux is not needed to run. So it can be deleted after compilation. The directories and files to be restored are:

/ tmp/bin points to / system/bin/lib points to / system/libetc/resolver to get back, nameserver 8.8.8.8/usr/bin points to / system/bin/usr/include points to / system/include/usr/lib points to / system/lib

Decompress otp_src_20.3.tar.gz, which does not support shadowbuild and configure, and directly cd src,sudo. / configure-prefix=/usr/local/cloudwall/-with-ssl=/system. If you do not add ssl, Uncaught error in rebar_core will appear later, and then make,make install

Now to compile mozjs, it will be used until python,python is compiled into ssl before pip can be installed, and then used in the next mozjs. Change the SSL section in Modules/Setup in the Python build directory to:

SSL=/system_ssl _ ssl.c\-DUSE_SSL-I $(SSL) / include-I $(SSL) / include/openssl\-L$ (SSL) / lib-lssl-lcrypto

If you install pip, you will need to use the original file / etc/resolver to resolve the download address. Install zip-unzip.tcz, directly cd js-1.85/js/src,./configure-prefix=/usr/local/cloudwall,make,make install, all the way to success. Note: do not download the source code package like mozjs-45.0.2.tar.bz2 here. Couchdb2 only requires 185s of spidermonkey js. Compiling mozjs 45 is much more troublesome. It requires gcc47,glibc2.12, and then cannot connect with couchdb. For example, it will appear and compile / src/couch_js/*c files. C contains the case where error: unknown type name xxx occurs in the C++ header file, which involves modifying the src/couch/rebar.config.script, but it is not successful in the end.

Next, when you compile couchdb,cd src,./configure-disable-docs and cannot execute rebar, you will find that it refers to / usr/bin. Restore the directory as mentioned at the beginning, and then find that the extracted apachecounch permissions are random. When all root,make is made, rebar will use erlang, set export PATH=$PATH:/usr/local/cloudwall/bin, and then make release, prompt that jsapi.h cannot be found, and modify src/couch/rebar.config.script:

{"linux", CouchJSPath, CouchJSSrc, [{env, [{"CFLAGS", JS_CFLAGS + + "- DXP_UNIX-I/usr/local/cloudwall/include/js"}, {"LDFLAGS", JS_LDFLAGS + + "- L/usr/local/cloudwall/lib-lm"}]}]}

Successful, prompts you to copy the generated rel to the destination folder.

Install cloudwall

Copy the generated rel to cloudwall:cp-R rel/* / usr/local/cloudwall, and install icu.tcz. Now, copy js libs to / usr/local/lib, and then

Change two 127.0.0.1 to 0.0.0.0 in / etc/default.ini

Cd / usr/local/cloudwall/rel/couchdb,./bin/couchdb, successful. Access, xxx:5984/_utils/#verifyinstall, enter fauxton, add the default administrative user at the lower left user, the user name must be admin, then add a database mineportal, and then create a document occurrence document editing area at the design of this database. Download

Https://cloudwall.me/cloudwall-2.2.json, open, copy and paste into the document editing area with noteplus, save and prompt for success, then visit the following page:

Xxx:5984/mineportal/_design/cw22/index.html

Enter the admin and password, inliner is the place to create the article, code is the place to create the codesippter, inliner file,gallery and so on are as complete as ocwp mineportal, a network disk facility provides. Its power is that it can inplace editor to generate app.

To facilitate startup, you can also find boot logic such as etc/init.d on the Internet.

This is the end of "how to install and use cloudwall on tinycolinux". Thank you for reading. If you want to know more about the industry, you can follow the website, the editor will output more high-quality practical articles for you!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.