mirror of
https://github.com/fluencelabs/gitbook-docs
synced 2025-06-21 10:41:41 +00:00
GitBook: [main] 53 pages and 14 assets modified
This commit is contained in:
committed by
gitbook-bot
parent
84e814d02d
commit
b383a8a319
.gitbook/assets
air_fold_4 (1) (2) (2) (3) (1).pngair_fold_4 (1) (2) (2) (3) (2).pngair_fold_4 (1) (2) (2) (3) (3).pngair_null_6 (1) (2) (2) (3) (1).pngair_null_6 (1) (2) (2) (3) (2).pngair_null_6 (1) (2) (2) (3) (3).pngair_sequential_2 (1) (1) (1) (1) (1) (1).pngair_sequential_2 (1) (1) (1) (1) (1) (2).png
building-a-frontend-with-js-sdk.mddevelopment_development
development_overview.md
development_reward_block_app
development_additional_concepts.mddevelopment_eth_calls.mddevelopment_persisting_blocks.mddevelopment_sqlite.md
developmet_build_modules.mdsummary.mdknowledge_knowledge
p2p.mdquick_start
quick_start_add_persistence
quick_start_building_from_multiple_services.mdquick_start_using_a_service.mdrecipes_recipes
research-papers-and-references.mdtutorials_tutorials
@ -1,8 +1,6 @@
|
||||
# Overview
|
||||
|
||||
|
||||
In the Quick Start section we incrementally created a distributed, database-backed request processing application using existing services with Aquamarine. Of course, we left a lot of detail uncovered including where the services we used came from in the first place. In this section, we tackle the very issue of development and deployment of service component.
|
||||
|
||||
|
||||
Before we proceed, please make sure your Fluence environment is [setup](../recipes_recipes/recipes_setting_up.md) and ready to go. Moreover, we are going to run our own Fluence node to test our services in a network environment. Please refer to the [Running a Local Fluence Node](../tutorials_tutorials/tutorial_run_local_node.md) tutorial if you need support.
|
||||
|
||||
|
Reference in New Issue
Block a user